differences in configure flags
James Gregurich
bayoubengal at mac.com
Wed Feb 2 14:54:40 PST 2011
a couple of questions:
Why doesn't CPPFLAGS contain ${output} like the other c-language flags?
append_list_to_environment_value configure "CFLAGS" ${output}${configure.cflags}
append_list_to_environment_value configure "CPPFLAGS" ${configure.cppflags}
append_list_to_environment_value configure "CXXFLAGS" ${output}${configure.cxxflags}
append_list_to_environment_value configure "OBJCFLAGS" ${output}${configure.objcflags}
from configure_main:
# add extra flags that are conditional on whether we're building universal
if {[variant_exists universal] && [variant_isset universal]} {
foreach flags {CFLAGS OBJCFLAGS} {
append_list_to_environment_value configure $flags ${configure.universal_cflags}
}
append_list_to_environment_value configure "CXXFLAGS" ${configure.universal_cxxflags}
append_list_to_environment_value configure "CPPFLAGS" ${configure.universal_cppflags}
append_list_to_environment_value configure "LDFLAGS" ${configure.universal_ldflags}
eval configure.pre_args-append ${configure.universal_args}
} else {
foreach {tool flags} {cc CFLAGS cxx CXXFLAGS objc OBJCFLAGS f77 FFLAGS f90 F90FLAGS fc FCFLAGS ld LDFLAGS} {
append_list_to_environment_value configure $flags [set configure.${tool}_archflags]
if {${configure.march} != {}} {
append_list_to_environment_value configure $flags "-march=${configure.march}"
}
if {${configure.mtune} != {}} {
append_list_to_environment_value configure $flags "-mtune=${configure.mtune}"
}
}
}
Why isn't CPPFLAGS being updated with the same info as the other c-language flags? Should it be?
-James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20110202/dba8a8d6/attachment-0001.html>
More information about the macports-dev
mailing list