Re: Linking a program with a directory??

On Fri, Jul 23, 2004 at 08:37:59PM +0200, Bram Moolenaar wrote:

[..]

>> What I am stuck on that main.c needs foo/foo.h to compile. So, I'd like
>> to add '-I../foo' when gcc compiles main.c. But I am at a loss!
>> add_INCLUDE, INCLUDE, add_CPPFLAGS, CPPFLAGS... neither has any effect.
>> How do I do it?
>
>Setting $INCLUDE should work.  What have you tried?

Yes, it does work. I am not sure what I did the first time around :-)

>> I have to say that the documentation seems to miss some really
>> essential parts here, doesn't it? A-A-P is a build tool, right? Why
>> not have some examples of what people do with build tools?
>> 
>>  - Linking to libraries, both in and outside of the build.
>>  - Hierarchical builds, with dependencies between targets in different
>>    directories (make is considered harmful because of its poor support
>>    for this, I hope AAP is better)
>
>Aap will take care of dependencies between sources and targets in
>different directories.  You just have to speficy what depends on what.
>
>You still have to specify where to look for include files, Aap can't
>guess where they are.

True, and I agree, that is what I expected AAP aap to do. However, the
examples that I have found in the documentation are either way too low
level (how to compile an executable from a single file linking with no
libraries) or unrelated to building executables (maintaining a website
in aap). What I am missing is something along the lines of what can be
found in Automake's info file or in make's manual. At least I am still
under the impression that aap aspires to be a better make than make (and
automake?) is, so why not have some examples of how to use it in places
where make and automake are used at the moment?

/M

-- 
Magnus Therning                    (OpenPGP: 0xAB4DFBA4)
[email protected]
http://magnus.therning.org/

Computers are useless. They can only give you answers.
     -- Pablo Picasso

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBAjZoiMWTaatN+6QRAudQAKDY0THvN6lle8+X8FkDD7slMiyuaQCgjWzr
Yv9arHSrQmQiBK7WdrrSVJE=
=bOWj
-----END PGP SIGNATURE-----