search for: xcodebuild

Dear All, Is there a way to convince xcodebuild to build bitcode files for LLVM for an arbitrary Xcode project? So far, I've been able to get xcodebuild to use LLVM by installing XCode 3.1 and using CC="llvm-gcc" on the command line. I've also managed to get LLVM bitcode generates for intermediate files by using "CC=...

On Sep 3, 2008, at 3:12 PM, John Criswell wrote: > Dear All, > > Is there a way to convince xcodebuild to build bitcode files for LLVM > for an arbitrary Xcode project? So far, I've been able to get > xcodebuild to use LLVM by installing XCode 3.1 and using CC="llvm-gcc" > on the command line. I've also managed to get LLVM bitcode generates > for intermediate files by...

...lped some. However, I'm now getting errors from libtool about an object being modified after free. Is libtool supposed to work with LLVM bitcode files? If so, would grabbing the latest source potentially fix the problem (I'm currently using XCode 3.1), or will I need a way to convince xcodebuild to use something other than libtool? -- John T. Ted Kremenek wrote: > On Sep 3, 2008, at 3:12 PM, John Criswell wrote: > > >> Dear All, >> >> Is there a way to convince xcodebuild to build bitcode files for LLVM >> for an arbitrary Xcode project? So far, I...

On Sep 3, 2008, at 3:12 PM, John Criswell wrote: > Is there a way to convince xcodebuild to build bitcode files for LLVM > for an arbitrary Xcode project? So far, I've been able to get > xcodebuild to use LLVM by installing XCode 3.1 and using CC="llvm-gcc" > on the command line. I've also managed to get LLVM bitcode generates > for intermediate files by...

...I'm now getting errors from > libtool about an object being modified after free. > > Is libtool supposed to work with LLVM bitcode files? If so, would > grabbing the latest source potentially fix the problem (I'm currently > using XCode 3.1), or will I need a way to convince xcodebuild to use > something other than libtool? > > -- John T. > > Ted Kremenek wrote: >> On Sep 3, 2008, at 3:12 PM, John Criswell wrote: >> >> >>> Dear All, >>> >>> Is there a way to convince xcodebuild to build bitcode files for >>> L...

...nja files CMake would generate so that would explain what you're seeing. Some more people (I think) have a separate xcode build directory purely for indexing/IDE but do their main builds in a make/ninja environment. Anyway, I've just generated an Xcode project myself and (by running "xcodebuild -list") there does appear to be an "xcodebuild -target check" (etc). I've not actually run them because at the moment I only have access to a laptop that would take quite a while to finish, but I think that's probably your best bet. Cheers. Tim.

On Sep 11, 2008, at 9:30 PM, Ted Kremenek wrote: > Hi John, > > I'm not certain if libtool works with LLVM bitcode files, and I don't > think that all of the tools that manipulate/inspect object files on > Mac OS X understand bitcode files either. Yes. Right now only ld recognizes LLVM bitcode files. > I suspect that this will > change over time. Yes. - Devang

Hi, I configured and built LLVM as follows on Mac OS 10.13.2: $ pwd <llvm-build-dir> $ cmake -G "Xcode" -DCMAKE_INSTALL_PREFIX=<llvm-install-dir> -DLLVM_ENABLE_PIC=0 <llvm-src-dir>/llvm $ xcodebuild -project LLVM.xcodeproj All binaries are in <llvm-build-dir>/Debug/bin. I am interested in using the output of llvm-config. Now, when I run $ <llvm-build-dir>/Debug/bin/llvm-config --cmakedir <llvm-build-dir>/Debug/lib/cmake/llvm But, $ ls -d `<llvm-build-dir>/Debug/bin...

...rial for installing wine: http://www.davidbaumgold.com/tutorials/wine-mac/ When I get to part 3 and it tells me to type the following code into terminal Code: $ sudo port install wine I get the following message: Code: xxx-xxx-macbook-pro:~ Kaoss$ sudo port install wine Password: Warning: xcodebuild exists but failed to execute Warning: Xcode appears to be installed but xcodebuild is unusable; some ports will likely fail to build. Warning: You may need to run `sudo xcode-select -switch /Applications/Xcode.app` Warning: The Command Line Tools for Xcode don't appear to be installed; most por...

...r's Delight i.e., ====== #include <stdlib.h> #include <stdint.h> uint32_t ror(uint32_t input, size_t rot_bits) { return (input >> rot_bits) | (input << ((sizeof(input) << 3) - rot_bits)); } ====== Then compile with (assuming you are on OS X): ====== ISYSROOT=$(xcodebuild -sdk macosx -version PlatformPath)/Developer/SDKs/MacOSX10.8.sdk $(xcrun -find clang) -isysroot $ISYSROOT ror.c -c -S -Os -o - ====== yielding an assembly output of: ====== .section __TEXT,__text,regular,pure_instructions .globl _rotr _rotr: ## @rotr .cfi_startp...

in C or C++, how can I get clang/llvm to try and do a "rotate". (want to test this code in the mips16 port) i.e. emit rotr node. tia. reed

...C++ code and gcc getting confused, but since this is an Xcode project I'm wondering how it ever worked, if it has. > In any event, if you want to compile flac on OSX, then just use > Terminal.app I'm not sure I can build a QT .component from the terminal without resorting to xcodebuild. The latest source seems to have had changes made to the Xcode project, which gives me hope that at one point, around this time in the summer, one year ago someone was able to successfully get it all to build :) Would appreciate any pointers in the direction I should be heading and where t...

...:24 PM *To:* llvm-dev *Subject:* [llvm-dev] llvm-config output on MacOS Hi, I configured and built LLVM as follows on Mac OS 10.13.2: $ pwd <llvm-build-dir> $ cmake -G "Xcode" -DCMAKE_INSTALL_PREFIX=<llvm-install-dir> -DLLVM_ENABLE_PIC=0 <llvm-src-dir>/llvm $ xcodebuild -project LLVM.xcodeproj All binaries are in <llvm-build-dir>/Debug/bin. I am interested in using the output of llvm-config. Now, when I run $ <llvm-build-dir>/Debug/bin/llvm-config --cmakedir <llvm-build-dir>/Debug/lib/cmake/llvm But, $ ls -d `<llvm-build-dir>/Deb...

...t; > #include<stdint.h> > > uint32_t ror(uint32_t input, size_t rot_bits) > { > return (input>> rot_bits) | (input<< ((sizeof(input)<< 3) - rot_bits)); > } > ====== > > Then compile with (assuming you are on OS X): > ====== > ISYSROOT=$(xcodebuild -sdk macosx -version PlatformPath)/Developer/SDKs/MacOSX10.8.sdk > $(xcrun -find clang) -isysroot $ISYSROOT ror.c -c -S -Os -o - > ====== > > yielding an assembly output of: > ====== > .section __TEXT,__text,regular,pure_instructions > .globl _rotr > _rotr:...

Please, can anybody show me the required steps for running the LLVM regression tests, or point me to a detailed doc? I read the available documentation in https://llvm.org/docs/TestingGuide.html <https://llvm.org/docs/TestingGuide.html> but that's mostly a general description on what’s available rather than an “guide”. This is what I tried: - Installed both LLVM and CLANG using

On 07-05-13 07:43, Martijn van Beurden wrote: > It's not that hard to repackage it, is it? > > Here you go: www.icer.nl/misc_stuff/flac.xcodeproj .zip I don't know what went wrong with that link, but it should be http://www.icer.nl/misc_stuff/flac.xcodeproj.zip -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Bill, > We use GNUmakefile to trigger using the build_gcc script. thanks for the explanation, but I still don't understand why it is done this way. Why not just get Apple people to run some script, rather than trying to have "make" automagically do an Apple build? > It's not > ideal, but it's all we have at the moment. For LLVM, we placed those > files

On Nov 25, 2012, at 6:49 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Sun, Nov 25, 2012 at 3:19 PM, Joe Abbey <jabbey at arxan.com> wrote: >> If cmake happens to detect GCC for the C compiler and Clang for the C++ >> compiler, then a manual override of either the C compiler or >> SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG is required. This has been

Sorry for the late response. You should check out CMAKE_TOOLCHAIN_FILE logic for Android platform - IIRC build rules for Android are much simpler than for Darwin/Linux, and assume that build tree will be properly configured to build a single compiler-rt runtime for a specific triple. Probably this is the approach you want to eventually use for another platforms. Also check out

...>> uint32_t ror(uint32_t input, size_t rot_bits) >> { >> return (input>> rot_bits) | (input<< ((sizeof(input)<< 3) - rot_bits)); >> } >> ====== >> >> Then compile with (assuming you are on OS X): >> ====== >> ISYSROOT=$(xcodebuild -sdk macosx -version PlatformPath)/Developer/SDKs/MacOSX10.8.sdk >> $(xcrun -find clang) -isysroot $ISYSROOT ror.c -c -S -Os -o - >> ====== >> >> yielding an assembly output of: >> ====== >> .section __TEXT,__text,regular,pure_instructions >> .globl _rot...