RE: Thanks it works, now what

See <wink2>

> Thanks for the answers everything looks good, but I'm still unsure of 
> how to solve question 1, handling the location of common includes. Ok, 
> I just read the documentation on startup, but I don't think that quite 
> solves my problem as it is too global. I will be using "aap" for many 
> disconnected projects but the startup technique looks to be designed 
> for "site" wide initialization, I want something "project" in scope.

What is a project scope?  The problem is that everyone has its own
definition of this.  Especially if you consider a sub-project to be a
project as well.

<wink2>
Agreed on persons trash is another's treasure.
</wink2>

<
> What I think I want is for aap to look for "family.aap" or 
> "project_root.aap" starting at the current location "." and use ".." 
> to look "up" until it finds it. Actually a "function" that was 
> ":hinclude xxx.aap" might do it. Where ":hinclude" is hierarchical 
> include.
> 
> Am I missing something, am I the only person who has this problem? 
> Maybe the solution is that my model is wrong and I need to change! As 
> always, any advice is appreciated.

One solution is to put a "project.aap" recipe in every directory.  In all
directories except the top one it contains ":include ../project.aap".  In
the top directory it contains your actual settings.

It does require adding more files, but in case a sub-project requires
specific settings you can cover them at the same time.

<wink2>
Yes, this was the technique I used with make and I didn't like it very much
and is one of the reasons I'm looking for another solution. I agree it can
be useful, but I'd rather not be "forced" to have the extra files.
</wink2>

Cheers,

Wink



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/