[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Hurd source tree; inter-directory dependencies
From: |
Ralf Wildenhues |
Subject: |
Re: Hurd source tree; inter-directory dependencies |
Date: |
Mon, 3 Apr 2006 18:07:57 +0200 |
User-agent: |
Mutt/1.5.11 |
Hi Bas,
* Bas Wijnen wrote on Mon, Apr 03, 2006 at 09:58:47AM CEST:
>
> In one of my projects, I use the nonrecursive approach, but I still have a
> Makefile.am per directory.
Yes, it's a good idea to group things this way (by using included
Makefile.am snippets)
> Automake obviously isn't built to support it, but
> it does work. If you're interested how it looks, check the Makefile.ams at
> http://pcbcn10.phys.rug.nl/svn/trunk/drivers/ (and its subdirectories).
It supports it, but it does require you to use the full paths.
Support for an `import' feature that would not require these
paths was thought of at some point IIRC, but deemed very
difficult to realize correctly.
> There's one major hack in there: automake doesn't support += on things like
> bin_PROGRAMS, so I had to create temporary variables for it and do
> bin_PROGRAMS = $(programs).
This sounds awfully like a bug in an old Automake version to me.
Which one do you use? If older than 1.9.6, please update.
> Also, in the included Makefile.ams you must
> remember to always use the full path (from the toplevel Makefile.am). And
> finally, my tree builds all the programs (and libraries) to top_builddir.
> Check out the nobase_ prefix if you don't want that.
Check out the Automake option subdir-objects, if you don't want that.
Cheers,
Ralf