From: john s. <sk...@us...> - 2009-10-08 20:48:57
|
On 09/10/2009, at 3:44 AM, Erick Tryzelaar wrote: > On Thu, Oct 8, 2009 at 5:06 AM, john skaller > <sk...@us...> wrote: >> >> Yeah, but only 32 bit. My gmp is only 64 bit. >> >> That --name=f64 option would be nice so I can build both. > > You could use "fbuild/fbuild-light --buildroot build/release/i386" and > "fbuild/fbuild-light --buildroot build/release/x86_64" to have > distinct build directories. It's a little ugly but it works. One thing > I've found myself doing is writing these little run-fbuild scripts > that have all these options saved in them. In my case, I've got: > > #!/bin/sh > #PYTHONPATH=fbuild/lib/fbuild python3.1 ./fbuild/fbuild-light \ > ./fbuild/fbuild-light \ > -I /opt/local/include \ > -I /opt/local/include/SDL \ > -L /opt/local/lib \ > --host-llvm-config=$HOME/llvm/llvm-build/Release/bin/llvm-config \ > $* > > > You could copy the same model, but build both 32bit and 64bit builds > at the same time. I'll see if I can get fbuild to directly support > universal binaries, then this won't matter. It does matter, because that's *another* platform: as a developer I don't want it to be transparent, I need to know what I'm running! But thanks, the --buildroot option is just what I wanted! -- john skaller sk...@us... |