I added an option to the configure script to link against gdk instead
of imlib2. Most people already have gdk installed so that way they can
use awesome without installing imlib2, and gdk's pixbuf was explicitly
designed to replace imlib2.
Also, a nice side effect is that GDK works directly with cairo
surfaces, so the process of loading images should be faster, although
since awesome does very little image loading it probably wont have a
noticable impact on performance, but it certainly won't hurt.
Signed-off-by: Julien Danjou <julien@danjou.info>
If xmlto is present, create a very simple example man page by
running 'xmlto man'. Only generate man pages at "make all" time
if this works.
The check is a little lenthy, so we might want to put it into
a separate .m4 file some time.
Signed-off-by: Julien Danjou <julien@danjou.info>
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.
Nikos Ntarmos
Julien Danjou
Alex Cornejo
Arnaud Fontaine
Hans Ulrich Niedermann