CPATH versus -I

[Michael Dickens]

qt4-mac luckily didn't use .cppflags or .ldflags -- it was using CPATH
and LIBRARY_PATH via configure.env and build.env, which I'm figuring out
how to move to compiler.cpath and compiler.library_path.  So at least
for qt4-mac this change is minimally risky, and will probably remove
some of the "conflicts" after all is said and done (which is a good
thing).  That said, modifying ports that do use cppflags and/or ldflags,
to use .cpath and .library_path, will certainly require testing -- but
the end result should be more robust to future conflicts and other port
changes. - MLD

On Sat, 19 Jun 2010 02:26 +1000, "Joshua Root" <jmr at macports.org> wrote:
> This is a risky change, which is why compiler.cpath and
> compiler.library_path have only been in trunk until the 1.9.0 release.
> Adding them doesn't seem to have broken much, but now we have to find
> out whether removing -I${prefix}/include from the default
> configure.cppflags and -L${prefix}/lib from configure.ldflags is as
> benign.
> 
> Individual ports can use *-delete to do this right now if they need to.
> That will certainly benefit a number of ports that like to compile/link
> against the previously installed version of themselves, like cyrus-sasl2.