>>>>> "Robert" == Robert Boehne <[EMAIL PROTECTED]> writes:
Robert> How flexible is automake/autoconf about what the directory
Robert> structure of a project looks like?
Automake 1.4 is fairly inflexible.
The cvs automake tries to be more flexible.
Robert> The package consists of 40 or so C++ shared libraries, each
Robert> one has a "source" directory that is basically empty, each
Robert> library has about 20 other directories that contain the source
Robert> for the shared object.
Are these other directories subdirectories of the library's source
directory? The cvs automake should be able to handle this (if not,
that is a bug).
Robert> project-root:
Robert> drv/ src/ inc/ make/ @host@/
You could probably do this somehow with a lot of hackery. But it
isn't the automake way -- in particular putting objects into the
`@host@' directory. Instead we encourage people to use the standard
GNU `non-srcdir' build feature.
Robert> Is it possible to have my top-level scripts and makefiles
Robert> in the above "make" directory? Or is it absolutely
Robert> necessary to have them in the "project-root" directory?
You pretty much have to have them in the top level.
Robert> Can I use a Makefile.am in one of the src/subpart
Robert> directories to create a Makefile in @host@/obj/subpart ?
Nope.
Robert> I won't even mention the headaches that I will encounter when
Robert> I go to link the C++ shared libraries... ;)
These are probably solved, at least if you refer to template
instantiation problems. You can set the `_AR' variable on a
per-library basis to the correct CC invocation.
Tom
