search for: dcmake_osx_deployment_target

..._DEPLOYMENT_TARGET is set to "10.8" during the build on > darwin12. > If I use... > > cmake -DLLVM_BUILD_32_BITS:BOOL=OFF -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_INSTALL_PREFIX=%p/opt/llvm-%v -DLLVM_ENABLE_ASSERTIONS=OFF -DCMAKE_BUILD_TYPE=Release -DCMAKE_OSX_SYSROOT:STRING=/ -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" .. Just to clarify, on darwin with cmake builds... -DCMAKE_OSX_SYSROOT:STRING=/ -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" ...is usually only used in packaging scripts to handle the case where the Command Line Tools is installed but the matching Xcode.app isn't pr...

..." > during the build on > > darwin12. > > If I use... > > > > cmake -DLLVM_BUILD_32_BITS:BOOL=OFF -DLLVM_TARGETS_TO_BUILD=X86 > -DCMAKE_INSTALL_PREFIX=%p/opt/llvm-%v -DLLVM_ENABLE_ASSERTIONS=OFF > -DCMAKE_BUILD_TYPE=Release -DCMAKE_OSX_SYSROOT:STRING=/ > -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" .. > > Just to clarify, on darwin with cmake builds... > > -DCMAKE_OSX_SYSROOT:STRING=/ -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" > > ...is usually only used in packaging scripts to handle the case where the > Command Line Tools is installed but the...

When lld-3.4 is added to the tools directory of the llvm source tree as lld, the resulting cmake build produces a huge number of static libs and bloats the overall package from... -rw-r--r-- 1 root wheel 86361440 Nov 19 21:09 llvm34_3.4-0_darwin-x86_64.deb to -rw-r--r-- 1 root wheel 495257452 Nov 19 20:49 llvm34_3.4-0_darwin-x86_64.deb Is this a known issue with the initial release of

...sw/lib". MACOSX_DEPLOYMENT_TARGET is set to "10.8" during the build on darwin12. If I use... cmake -DLLVM_BUILD_32_BITS:BOOL=OFF -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_INSTALL_PREFIX=%p/opt/llvm-%v -DLLVM_ENABLE_ASSERTIONS=OFF -DCMAKE_BUILD_TYPE=Release -DCMAKE_OSX_SYSROOT:STRING=/ -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING="" .. ...the build completes but setting -DCMAKE_OSX_DEPLOYMENT_TARGET to a null string hasn't been required in the past. What happens to your cmake build if you set the MACOSX_DEPLOYMENT_TARGET target environmental? You should see the failure... [ 54%] Building CXX object pr...

lld definitely shouldn't be that big. I would expect 10MB at most. Can you check whether something weird is happening, like lld being built with debug info? -- Sean Silva On Wed, Nov 20, 2013 at 10:15 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > When lld-3.4 is added to the tools directory of the llvm source tree > as lld, the resulting cmake build produces a huge

This file is for configure+make build, not CMake, so I'm not sure why it's being included into your build (these failures aren't reproducible for me). Can you please list the exact steps you're doing to build LLVM with CMake and make sure you don't have additional CFLAGS (LDFLAGS etc) defined? On Mon, Nov 11, 2013 at 6:16 PM, Jack Howarth <howarth at bromo.med.uc.edu>

Hi Jack, Are you packaging all the static libraries that lld produces as part of the package ? PS : When I build on x86_64, I only get a 9M image for lld. Thanks Shankar Easwaran On 11/20/2013 9:15 AM, Jack Howarth wrote: > When lld-3.4 is added to the tools directory of the llvm source tree > as lld, the resulting cmake build produces a huge number of static libs and > bloats

...YLIB:BOOL=ON -DCOMPILER_RT_ENABLE_IOS:BOOL=OFF -DLLVM_ENABLE_FFI=ON -DFFI_INCLUDE_DIR=/sw/include -DFFI_LIBRARY_DIR=/sw/lib -DLLVM_LIT_ARGS:STRING=-v -DPYTHON_EXECUTABLE:FILEPATH=/sw/bin/python2.7 -DLIBOMP_OSX_ARCHITECTURES=x86_64;i386 -DLLVM_ENABLE_ASSERTIONS:BOOL=OFF -DCMAKE_OSX_SYSROOT:STRING=/ -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING= -DLLVM_TARGETS_TO_BUILD=X86;PowerPC;ARM -DCMAKE_INSTALL_PREFIX:PATH=/sw/opt/llvm-6.0 -DCMAKE_BUILD_TYPE:STRING=Release -DCMAKE_C_FLAGS=-fno-common -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON -DCMAKE_CXX_FLAGS=-fno-common -DCMAKE_SHARED_LINKER_FLAGS= -L/sw/lib -DCMAKE_MODULE_LINKER_FLAGS= -L/s...

...F >> -DLLVM_ENABLE_FFI=ON -DFFI_INCLUDE_DIR=/sw/include >> -DFFI_LIBRARY_DIR=/sw/lib -DLLVM_LIT_ARGS:STRING=-v >> -DPYTHON_EXECUTABLE:FILEPATH=/sw/bin/python2.7 >> -DLIBOMP_OSX_ARCHITECTURES=x86_64;i386 -DLLVM_ENABLE_ASSERTIONS:BOOL=OFF >> -DCMAKE_OSX_SYSROOT:STRING=/ -DCMAKE_OSX_DEPLOYMENT_TARGET:STRING= >> -DLLVM_TARGETS_TO_BUILD=X86;PowerPC;ARM -DCMAKE_INSTALL_PREFIX:PATH=/sw/opt/llvm-6.0 >> -DCMAKE_BUILD_TYPE:STRING=Release -DCMAKE_C_FLAGS=-fno-common >> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON -DCMAKE_CXX_FLAGS=-fno-common >> -DCMAKE_SHARED_LINKER_FLAGS= -L/sw...

On Sat, Oct 14, 2017 at 11:25 AM, Don Hinton <hintonda at gmail.com> wrote: > Hi Jack: > > Yes, I was just looking at that. Seems like TableGen wasn't done along > with the rest of llvm. I'll work up a complete patch shortly. > > Btw, I'm curious how this happened. Do you have a stale CMakeCache.txt by > any chance? You might check the value for