Dominique Devienne-2 wrote:
>
> Sorry, I assumed you knew about Ant's import. It can only be used at
> the top level of a build file.
>
> CppTasks supports defining named compiler/linker configurations (with
> nested includepath and all), which you'd put into a common build file,
> that you'd import from all your 40 component build files, in which
> you'd reuse the named configs inside <cc>. That's what I was referring
> to.
>
Thanks Dominique, it sounds like that's what I want.
Yea, I should have prefaced all this with: I am not very familiar with ant,
although I have a fairly complex working example in front of me.
Could someone please provide me a syntactical example of "defining named
configurations" and how to reference them in the <cc> tag. Sorry, but I'm
in need of a bit of hand-holding. Thanks =)
Thank you,
Glen
--
View this message in context:
http://www.nabble.com/Help-with-C%2B%2B-includepaths---Can-I-use-wildcards--make-a-external-repository-list--tp20584286p20588748.html
Sent from the Ant - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
