yes. I am aware of that one. I've seen in used in terms of running tests in icu. I had to switch it off for the cross-compile of icu. when configured with --host, icu requires a native build to be specified and it runs the tests as part of the native build.
On Feb 3, 2011, at 7:18 PM, Joshua Root wrote: > On 2011-2-4 14:07 , James Gregurich wrote: >> ok. I will continue running tests on what I have to see what works and what >> doesn't work. I have the thing working for 3 different ports with no >> unreasonable modifications to the port files. There is no point to starting >> over with a new strategy if this one is working....particularly one that >> would mean much more complex port files. >> >> >> The key is running the configure scripts through muniversal and setting the >> the -host option on the configure script. These projects appear to be >> designed to cross-compile you just have to pass the right options in. >> muniversal builds one architecture at a time...which is exactly what is >> needed for the configure scripts to work right on cross-compiling. > > You'll notice muniversal has an option called merger_must_run_binaries. > Anything that needs this to be set will not cross compile. > > - Josh _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
