| 1 | Where's the configure script? |
|---|
| 2 | |
|---|
| 3 | After installing the GNU autotools suite, execute the following |
|---|
| 4 | commands to generate the configure script (and other necessary |
|---|
| 5 | generated files): |
|---|
| 6 | aclocal |
|---|
| 7 | libtoolize |
|---|
| 8 | automake -a |
|---|
| 9 | automake |
|---|
| 10 | autoconf |
|---|
| 11 | |
|---|
| 12 | |
|---|
| 13 | Why aren't the configure script and other generated files in the |
|---|
| 14 | CVS repository? |
|---|
| 15 | |
|---|
| 16 | Because they are generated files. Why save a version history for |
|---|
| 17 | them? Further, some of the above commands get re-run automatically |
|---|
| 18 | when Makefile.am's are changed. This could lead to compatibility |
|---|
| 19 | problems if some of the generated files in the CVS repository are |
|---|
| 20 | from a different version of the GNU autotools. |
|---|
| 21 | |
|---|
| 22 | |
|---|
| 23 | Aren't we requiring users to have GNU autotools installed in order |
|---|
| 24 | to configure CGM? |
|---|
| 25 | |
|---|
| 26 | No. Developers must have the autotools installed. When creating a |
|---|
| 27 | tarball for distribution of CGM, the commands below should be run |
|---|
| 28 | and the generated files included in the tarball. |
|---|
| 29 | |
|---|
| 30 | |
|---|
| 31 | What needs to be done to prepare CGM for distribution as a tarball? |
|---|
| 32 | |
|---|
| 33 | Check out a clean copy of CGM. |
|---|
| 34 | Execute the following commands in the top-most directory: |
|---|
| 35 | aclocal |
|---|
| 36 | libtoolize -c -f |
|---|
| 37 | automake -a -c |
|---|
| 38 | automake -i |
|---|
| 39 | autoconf -f |
|---|
| 40 | |
|---|
| 41 | |
|---|
| 42 | How what to the extra flags mean in the autotools commands? |
|---|
| 43 | |
|---|
| 44 | The '-c' flag means that files in config_aux should be copies |
|---|
| 45 | of those that were installed with the autotools, rather than |
|---|
| 46 | symlinks to them. The '-f' flag causes any existing files to |
|---|
| 47 | be overwritten. The makefiles generated by automake and |
|---|
| 48 | configure will, by default, generate source depenedency |
|---|
| 49 | information (like makedepend) on the fly. This is very useful |
|---|
| 50 | for developers but doesn't work on all platforms. The '-i' |
|---|
| 51 | option causes automake to generate makefiles with a static |
|---|
| 52 | list of source dependencies embedded in them. |
|---|
| 53 | |
|---|
| 54 | |
|---|
| 55 | Which files are generated by each of the above commands? |
|---|
| 56 | |
|---|
| 57 | aclocal: aclocal.m4 |
|---|
| 58 | libtoolize: config_aux/config.guess |
|---|
| 59 | config_aux/config.sub |
|---|
| 60 | config_aux/ltmain.sh |
|---|
| 61 | automake -a: config_aux/install-sh |
|---|
| 62 | config_aux/mkinstalldirs |
|---|
| 63 | config_aux/missing |
|---|
| 64 | automake: the Makefile.in from the Makefile.am in each directory. |
|---|
| 65 | autoconf: configure |
|---|
| 66 | configure: config.make |
|---|
| 67 | libtool |
|---|
| 68 | the Makefile from the Makefile.in in each directory. |
|---|