On Aug 31, 2011, at 02:13, j...@macports.org wrote:
> Revision: 83390
> http://trac.macports.org/changeset/83390
> Author: j...@macports.org
> Date: 2011-08-31 00:13:22 -0700 (Wed, 31 Aug 2011)
> Log Message:
> -----------
> glew: update to 1.7.0, rev bump dependents
> variant universal {
> patchfiles-append patch-Makefile.diff
> - build.args-append CFLAGS.ARCH="${configure.universal_cflags}" \
> - LDFLAGS.ARCH="${configure.universal_ldflags}"
> }
> +build.args-append CFLAGS.ARCH="[get_canonical_archflags cc]" \
> + LDFLAGS.ARCH="[get_canonical_archflags ld]"
>
...get_canonical_archflags takes an argument? Oh yes I see, it defaults to cc
and uses that to determine which variable to use to get the archflags from.
But as you remember from the conversation leading up to you creating the
get_canonical_archflags function, I didn't understand why we have separate
variables at all. Under what circumstances would configure.cc_archflags be
different from configure.cxx_archflags or configure.ld_archflags? Do we really
need that distinction?
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
