CC Program for compiling C programs; default ‘cc’. CXX Program for compiling C++ programs; default ‘g++’. CPP Program for running the C preprocessor, with results to standard output; default ‘$(CC) -E’.
Based on this statement, it seems to me that CPP needs to have the arch flag. However, I can set it up so that it only gets added if the build is a cross-compile. That way, it shouldn't affect a normal default build. I think that it is an accident that the system works without the -arch flag when building ppc/intel on MacOSX. I think that I'll change the expat port to use muniversal. Is this reasonable? On Feb 3, 2011, at 11:41 AM, James Gregurich wrote: > I found the following: > > http://stackoverflow.com/questions/495598/difference-between-cppflags-and-cxxflags-in-gnu-make > http://www.gnu.org/software/make/manual/html_node/Implicit-Variables.html#Implicit-Variables > > > > On Feb 3, 2011, at 11:35 AM, James Gregurich wrote: > >> >> ok. ignoring the practical perspective, what is conceptually correct? What >> is the design purpose of CPPFLAGS and CXXFLAGS In the configure script >> system? >> >> >> On Feb 3, 2011, at 11:24 AM, Daniel J. Luke wrote: >> >>> On Feb 3, 2011, at 2:14 PM, James Gregurich wrote: >>>> >>>> I need clear guidance on where to go on this point. Should macports be >>>> patched to add the missing flags to CPPFLAGS or should the expat folks be >>>> approached about corrections to their configure script. >>> >>> I don't have an easy answer but... >>> >>> You probably need a larger sample size to determine if adding arch args to >>> CPPFLAGS is a good idea or not. As a practical matter, it's only worth >>> doing if it solves more problems than it causes. >> >> _______________________________________________ >> macports-dev mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev > > _______________________________________________ > macports-dev mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
