Hi, folks.
I have a directory under which there are multiple nested directories,
sometimes containing a makefile.
At present, we handle these by calling <exec> on each one in turn. This
uses around three lines of antfile for every makefile, and the number of
directories is steadily increasing. The current system also has a flaw
that a developer may add a makefile to the compile section while
forgetting to add it to the clean section.
Today I discovered the <apply> task, and thought it might be the way out
of this predicament. However, that task becomes useless very quickly.
The problem is that make needs to be run in the same directory as the
makefile. The <apply> task allows me to specify a directory to run the
command, but as far as I can tell, I can't specify to run it in the same
directory as the file.
Obviously I can work around this by having some kind of master makefile
which calls all the makefiles under it, but then I still have to
manually add something to that file whenever I add new source.
Another option might be using ant-contrib's <cc> task, but I have found
some serious issues when trying to use that task with C++ code.
So, how do other people work around this limitation?
Daniel
--
Daniel Noll
Nuix Pty Ltd
Suite 79, 89 Jones St, Ultimo NSW 2007, Australia Ph: +61 2 9280 0699
Web: http://www.nuix.com.au/ Fax: +61 2 9212 6902
This message is intended only for the named recipient. If you are not
the intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of this
message or attachment is strictly prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
