search for: universal_sdk_path

...eveloping an application on a >> 10.5 machine but want to target the 10.4 SDK. Is there a magic >> incantation for the llvm configure script to set the sysroot path, >> equivalent to e.g. --with-sysroot "/Developer/SDKs/MacOSX10.4u.sdk"? >> > Try 'make UNIVERSAL_SDK_PATH=/Developer/SDKs/MacOSX10.4u.sdk/'. > > There are some comments in llvm/Makefile.rules that can help, Note that you don't have to use 10.4 SDK to target Tiger. You just have to set the "macosx version min" (either using the gcc flag - mmacosx-version-min=10.4 or using the...

Hi, For the record, adding UNIVERSAL_SDK_PATH=/Developer/SDKs/MacOSX10.4u.sdk/ was insufficient to restrict the .a/.o files to link against the 10.4 sdk, but env MACOSX_DEPLOYMENT_TARGET=10.4 make did the trick. Thanks! On Jan 14, 2009, at 1:29 PM, Jean-Daniel Dupas wrote: > > Le 14 janv. 09 à 21:48, Chris Lattner a écrit : >...

...se, using the following commands to try and force LLVM to build against the OSX 10.4 sdk (I am actually doing this on an OS X 10.5.8 system): env MACOSX_DEPLOYMENT_TARGET=10.4 ./configure --enable-targets=x86 -- enable-jit --enable-optimized --enable-pic env MACOSX_DEPLOYMENT_TARGET=10.4 make UNIVERSAL_SDK_PATH=/Developer/ SDKs/MacOSX10.4u.sdk/ This seems to work fine. However, my project is a dynamic library in which LLVM/Clang are embedded for adding runtime JIT capability to an existing application, but in attempting to build, I get a linker error on _backtrace from LLVMSystem.a. Is this a si...

...are concerned, except that -mmacosx-version-min is set to the host’s OS version, not that of the SDK, causing errors when it tries to link against 10.6’s versions of libraries instead of 10.5’s. This patch appears to solve that; it uses the OS version from the SDK path for -mmacosx-version-min if UNIVERSAL_SDK_PATH is specified. -------------- next part -------------- A non-text attachment was scrubbed... Name: Makefile.rules.patch Type: application/octet-stream Size: 1068 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091222/1d666337/attachment.obj> ------------...

...g commands to try and force LLVM to build against the > OSX 10.4 sdk (I am actually doing this on an OS X 10.5.8 system): > > env MACOSX_DEPLOYMENT_TARGET=10.4 ./configure --enable-targets=x86 -- > enable-jit --enable-optimized --enable-pic > env MACOSX_DEPLOYMENT_TARGET=10.4 make UNIVERSAL_SDK_PATH=/Developer/ > SDKs/MacOSX10.4u.sdk/ > > This seems to work fine. > > However, my project is a dynamic library in which LLVM/Clang are > embedded for adding runtime JIT capability to an existing > application, but in attempting to build, I get a linker error on > _back...

Sorry if this is a newb q... I'm developing an application on a 10.5 machine but want to target the 10.4 SDK. Is there a magic incantation for the llvm configure script to set the sysroot path, equivalent to e.g. --with-sysroot "/Developer/SDKs/MacOSX10.4u.sdk"? Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

...a newb q... I'm developing an application on a 10.5 > machine but want to target the 10.4 SDK. Is there a magic > incantation for the llvm configure script to set the sysroot path, > equivalent to e.g. --with-sysroot "/Developer/SDKs/MacOSX10.4u.sdk"? > Try 'make UNIVERSAL_SDK_PATH=/Developer/SDKs/MacOSX10.4u.sdk/'. There are some comments in llvm/Makefile.rules that can help, -Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090114/d028f5b9/attachment.html>

...re than a single -arch flag. As I said before -arch ppc -arch i386 -arch x86_64. This results in x86_64 binaries only, unfortunately. However… > Daniel's comments are also good. …success! > export UNIVERSAL=true > export UNIVERSAL_ARCH="i386 x86_64 ppc ppc64" > export UNIVERSAL_SDK_PATH=/Developer/SDKs/MacOSX10.5.sdk/ > export CFLAGS="-mmacosx-version-min=10.5" > export CXXFLAGS="-mmacosx-version-min=10.5" > > ./configure --enable-optimized --enable-jit --enable-targets=x86,x86_64,powerpc > make libs-only I suspect the problem with my earlier...

On Dec 21, 2009, at 3:39 PM, Rob Rix wrote: >> Anyhow, Rob, best bet is to just use -arch to build everything up. lipo knows what needs to happen. > > Unfortunately that doesn’t appear to be enough; using -arch in CFLAGS (and CXXFLAGS) and not using --build or --host builds for x86_64 no matter what you specify for the architecture (in my case, the documented i386 and ppc). >

Hello, I’ve spent the past day or so attempting to get LLVM’s libraries built as a Mac OS X-style universal binary, the first step of which is to get them built for each component architecture (i386, x86_64, ppc, and ppc64). The first two are straightforward as I am working on an x86_64 Mac (running Mac OS X 10.6, which corresponds to Darwin 10), but building ppc binaries has thus far eluded me.