7.5 Frequently Asked Questions

back: programs and libraries
forward: multiple directories
 
fastback: multiple directories
up: introducing gnu automake
fastforward: bootstrapping
top: autoconf, automake, and libtool
contents: table of contents
index: index
about: about this document

Experience has shown that there are several common questions that arise as people begin to use automake for their own projects. It seemed prudent to mention these issues here.

Users often want to make a library (or program, but for some reason it comes up more frequently with libraries) whose sources live in subdirectories:

 
 lib_LIBRARIES = libsub.a libsub_a_SOURCES = subdir1/something.c ... 

If you try this with Automake 1.4, you'll get an error:

 
 $ automake automake: Makefile.am: not supported: source file subdir1/something.c is in subdirectory 

For libraries, this problem is mostly simply solve by using libtool convenience libraries. For programs, there is no simple solution. Many people elect to restructure their package in this case.

The next major release of Automake addresses this problem.

Another general problem that comes up is that of setting compilation flags. Most rules have flags--for instance, compilation of C code automatically uses `CFLAGS' . However, these variables are considered user variables. Setting them in `Makefile.am' is unsafe, because the user will expect to be able to override them at will.

To handle this, for each flag variable, Automake introduce an `AM_' version which can be set in `Makefile.am' . For instance, we could set some flags for C and C++ compilation like so:

 
 AM_CFLAGS = -DFOR_C AM_CXXFLAGS = -DFOR_CXX 

Finally, people often ask how to compile a single source file in two different ways. For instance, the ` etags .c' file which comes with Emacs can be compiled with different `-D' options to produce the etags and ctags programs.

With Automake 1.4 this can only be done by writing your own compilation rules, like this:

 
 bin_PROGRAMS = etags ctags etags_SOURCES = etags.c ctags_SOURCES = ctags_LDADD = ctags.o etags.o: etags.c $(CC) $(CFLAGS) -DETAGS ... ctags.o: etags.c $(CC) $(CFLAGS) -DCTAGS ... 

This is tedious and hard to maintain for larger programs. Automake 1.5 will support a much more natural approach:

 
 bin_PROGRAMS = etags ctags etags_SOURCES = etags.c etags_CFLAGS = -DETAGS ctags_SOURCES = etags.c ctags_CFLAGS = -DCTAGS 

This document was generated by Gary V. Vaughan on May, 24 2001 using texi2html


GNU Autoconf, Automake and Libtool
GNU Autoconf, Automake, and Libtool
ISBN: 1578701902
EAN: 2147483647
Year: 2002
Pages: 290

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net