[Fink-devel] Re: disabling /usr/local/include

[Matthias Neeracher]

I can see some value in disabling /usr/local/include (shouldn't we also 
disable /usr/local/lib ?), but I think putting %p/include and %p/lib at 
the end of our search paths rather than the beginning is going to cause 
us trouble: Wouldn't we be putting ourselves at the mercy of anything 
that Apple decides to ship in a new OS version? What benefit would we 
get from the different search order?

What if we make CPPFLAGS=-I%p/include -DLOCAL_INCLUDE_DIR=\%p/include ?

That way, %p/include would theoretically be searched twice, but in 
practice, the second time wouldn't actually matter, since any 
successful #include would already be done by then.

Matthias



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel