differences in configure flags

[James Gregurich]

A follow-up:  This questions has to do with the loop in the else-block. the if-block does modify CPPFLAGS.

On Feb 2, 2011, at 2:54 PM, James Gregurich wrote:

> 
> 
> 
>         # 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
> 
>  
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20110202/f40a3c09/attachment.html>