Changes between Version 5 and Version 6 of pm-autotools


Ignore:
Timestamp:
May 31, 2006 1:22:37 PM (14 years ago)
Author:
guest
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • pm-autotools

    v5 v6  
    2727== The Makefile.am Files ==
    2828
    29 The Makefiles are generated by {{{automake}}} based on {{{Makefile.am}}} input files.  Those usually contain information on what is to be compiled (e.g., program, library) and what source files are required for each, where things should be installed. etc.  One can also add regular Makefile rules that will copied verbatum into the final Makefile.
     29The Makefiles are generated by {{{automake}}} based on {{{Makefile.am}}} input files.  Those usually contain information on what is to be compiled (e.g., program, library) and what source files are required for each, where things should be installed. etc.  One can also add regular Makefile rules that will copied verbatim into the final Makefile.
    3030
    3131In a typical COIN project we have a number of different types of {{{Makefile.am}}}, depending on what the purpose of the corresponding directory is:
     
    3333 * '''Base directory Makefile.am''':   Even though this generates the only Makefile a user will usually work with, it is very simple.  It mainly defines, which subdirectories {{{make}}} should recurse into, and it typically define additional targets, such as {{{tests}}} which runs {{{make test}}} in all subdirectories that have tests.  [wiki:pm-base-make The example Makefile.am for the base directory is discussed here.]
    3434
    35  * '''Project main directory Makefile.am''':  In each projects main directorty (the subdirectories under the base directory, such as {{{Cpl}}} and {{{CoinUtils}}} in the [wiki:user-directories directory structure example] is the Makefile that takes care of project specific main things, such defining how {{{make test}}} is run, what extra files are to be included in a tarball created by {{{make dist}}}.  It also knows, into which source code directories {{{make}}} should recurse in order to build everything that project has to provide.  [wiki:pm-project-make The example main Makefile.am for a project is discussed here.]
     35 * '''Project main directory Makefile.am''':  In each projects main directory (the subdirectories under the base directory, such as {{{Cpl}}} and {{{CoinUtils}}} in the [wiki:user-directories directory structure example] is the Makefile that takes care of project specific main things, such defining how {{{make test}}} is run, what extra files are to be included in a tarball created by {{{make dist}}}.  It also knows, into which source code directories {{{make}}} should recurse in order to build everything that project has to provide.  [wiki:pm-project-make The example main Makefile.am for a project is discussed here.]
    3636
    3737 * '''Source code directory Makefile.am files''': This is where the real stuff happens.  Here one specifies what is to be built, what source files are required for this, where (and whether) the compiled files are to be installed.  [wiki:pm-source-make The Makefile.am files for the source code directories are discussed here.]