Updates awesome-version.h every time the version number has
actually changed. The normal C header deps will then trigger
the appropriate rebuilds.
Signed-off-by: Julien Danjou <julien@danjou.info>
Use information autoconf determines anyway (machine type
building for, name of machine building on).
Only print build information if it is actually available (defined).
Add descriptions to all AC_DEFINE* macro definitions.
Signed-off-by: Julien Danjou <julien@danjou.info>
Use a single script to generate the version number from git. This script
* strips the v from the start of the "git describe" output
* changes all "-" occurences to "."
* does NOT create a properly sortable version number from "2.1-rc2"
type "git describe" output
* does NOT generate a "proper" "1.2.3" type version number under any
circumstances
* will generate "2.1" in case the "git describe" output is "2.1"
These policy might need closer adaption to awesome's tagging habit
some time.
In dist tarballs, ship a "version-stamp" file with the package version
in it. If the "version-stamp" file is present (i.e. if it is a source
tree from a dist tarball), no git checks will be performed.
Concept from autoconf, but code written from scratch to match
awesome's requirements.
Signed-off-by: Julien Danjou <julien@danjou.info>
awesome's default compiler flags work only with gcc, so we only use
them if gcc is detected.
Additionally, you can now avoid using these default flags by adding
AWESOME_CFLAGS="" to your make command lines.
Hans Ulrich Niedermann
Julien Danjou