On Apr 24, 2009, at 02:26, [email protected] wrote:
Revision: 50072
http://trac.macports.org/changeset/50072
Author: [email protected]
Date: 2009-04-24 00:26:05 -0700 (Fri, 24 Apr 2009)
Log Message:
-----------
build.env is broken, work around it
Modified Paths:
--------------
trunk/dports/x11/rox-filer/Portfile
Modified: trunk/dports/x11/rox-filer/Portfile
===================================================================
--- trunk/dports/x11/rox-filer/Portfile 2009-04-24 07:24:42 UTC
(rev 50071)
+++ trunk/dports/x11/rox-filer/Portfile 2009-04-24 07:26:05 UTC
(rev 50072)
@@ -47,8 +47,8 @@
}
}
-build.env CC=${configure.cc} CPPFLAGS=${configure.cppflags}
LDFLAGS=${configure.ldflags}
-build { system "cd ${worksrcpath}; ./ROX-Filer/AppRun --compile $
{configure.args}" }
+#build.env CC=${configure.cc} CPPFLAGS=${configure.cppflags}
LDFLAGS=${configure.ldflags}
+build { system "cd ${worksrcpath}; CC=${configure.cc} CPPFLAGS=\"$
{configure.cppflags}\" LDFLAGS=\"${configure.ldflags}\" ./ROX-Filer/
AppRun --compile ${configure.args}" }
build.env isn't broken, but it isn't used if you override the build
phase, right?
Why not use the default build phase? Untested:
build.env ${configure.env}
build.cmd ./ROX-Filer/AppRun
build.args --compile ${configure.args}
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
