similar to: [LLVMdev] Running external build tool in Xcode?

On Oct 7, 2008, at 12:40 AM, Cloud Strife wrote: > Hi everyone. > I am using Mac OS X to inspect the llvm source code. > Although the make command works perfectly when compiling the source > code, the Xcode tool prompted me: > > Makefile:26: Makefile.config: No such file or directory > Makefile:58: /Makefile.rules: No such file or directory > > I downloaded the latest

Hello all, I have replaced the llvm-gcc shipped with the Xcode by the latest version and I was wondering if I have missed something... (everything *seems* to work). Here's what I did: 0. Checkout LLVM (and clang) + llvm-gcc 1. Build LLVM (with clang) and install into /Developer/usr/local : # mkdir llvmobj # cd llvmobj # CC=gcc-4.2 CXX=g++-4.2 ../llvm/configure

Those look like the linker is being passed the same .o file built twice, ex: ../Objects-normal/x86_64/asan_globals_test.o ../lib/asan/tests/asan_globals_test.cc.asan.o So, the symbols are colliding. Something is set up wrong in the xcode project. -Nick On Dec 19, 2012, at 9:48 AM, Relph, Richard wrote: > Following a blend of instructions on 3 web pages, I have succeeded in getting LLVM

I've been using make to build llvm but use Xcode for most other projects I work on. I decided to try running cmake to build an xcode project for llvm. The results were disappointing. The generated xcode project does not encode that executables link with static libraries. Instead, the static libraries are snuck in under "Other linker flags", then some pre- and post- scripts on

Jonathan Ragan-Kelley <katokop1 <at> gmail.com> writes: > > Slightly off-topic, but I imagine this crowd must have some experience > using Xcode 4 for projects linking to LLVM. I've actually started > using Xcode 4 as an IDE for C/C++ development thanks to the vastly > improved code analysis-based tools it's inherited largely thanks to > LLVM. But,

Following a blend of instructions on 3 web pages, I have succeeded in getting LLVM 3.2 (with clang, extras, and compiler-rt) building - but not testing - on Xcode. I used CMake 2.8.10 GUI to create the Xcode project file. Below are my notes. First, I believe CMake ends up setting things up so that Xcode has 1 warning after scanning the project having to do with hires images or some such… it takes

Different, but still failing (this time with Xcode 4.4…) /Users/rrelph/llvm/tot/xcode/bin/Debug/clang sanitizer_allocator_test.cc.i386.o sanitizer_common_test.cc.i386.o sanitizer_flags_test.cc.i386.o sanitizer_libc_test.cc.i386.o sanitizer_list_test.cc.i386.o sanitizer_printf_test.cc.i386.o sanitizer_stackdepot_test.cc.i386.o sanitizer_test_main.cc.i386.o gtest-all.cc.i386.o

----- Original Message ---- > From: Óscar Fuentes <ofv at wanadoo.es> > To: Samuel Crow <samuraileumas at yahoo.com> > Cc: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Sent: Wed, January 5, 2011 5:00:00 PM > Subject: Re: Build problems and workarounds with CMake and XCode > > Samuel Crow <samuraileumas at yahoo.com> writes: > >

Hi all In order to get ready for the upcoming final 9.0 release code I have now switched to the 'release/9.x' branch that I pulled from github. Unfortunately, after running cmake in the usual way, I found that many xcode schemes are missing on the resulting project. Particularly, I added -DLLVM_ENABLE_PROJECTS=clang to the terminal command line. The logs correctly state that ‘clang

Hi, I am trying to use the new LLVM-2.7 release in Xcode for my analysis and development. However, I do not see the top level Xcode directory as in LLVM-2.6. Can someone tell me how to develop on top of LLVM-2.7 using Xcode? Best Regards, Raj

Samuel Crow <samuraileumas at yahoo.com> writes: [snip] > I tried making a separate build of LLVM SVN in XCode using build files created > with CMake. Surprisingly, it worked better than Eclipse! The Build_All target > completed its build. The install target was another story though. First of > all, the commands to install with the terminal command-line needed to be

The ability to archive object files generated with -flto under LLVM.org clang 3.9.0 or 4.0svn trunk is broken against the currently shipping Xcode releases including the upcoming Xcode 8.1 GM. https://llvm.org/bugs/show_bug.cgi?id=30791 $ clang-3.9 -flto -O1 -c *.i $ ar cr libtar.a paxerror.o paxexit-status.o paxnames.o rtapelib.o stdopen.o wordsplit.o xattr-at.o error: Unknown attribute kind

> On Oct 26, 2016, at 8:06 AM, Jack Howarth via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The ability to archive object files generated with -flto under > LLVM.org clang 3.9.0 or 4.0svn trunk is broken against the currently > shipping Xcode releases including the upcoming Xcode 8.1 GM. > > https://llvm.org/bugs/show_bug.cgi?id=30791 > > $ clang-3.9

Hi Richard! On Thu, Dec 20, 2012 at 12:48 AM, Nick Kledzik <kledzik at apple.com> wrote: > Those look like the linker is being passed the same .o file built twice, > ex: > ../Objects-normal/x86_64/asan_globals_test.o > ../lib/asan/tests/asan_globals_test.cc.asan.o > > So, the symbols are colliding. Something is set up wrong in the xcode > project. > > -Nick

Hey, My projects are not compiling on 10.5 using llvm-gcc 4.2 in Xcode 3.1.4. These are caused by some llvm bugs that are now fixed. Since Apple will not release a Xcode update for 10.5, I am trying to compile a recent version of llvm-gcc 4.2 (from the LLVM 2.7 branch - but I could use ToT if this helps) to use on 10.5 intel. I easily built llvm-gcc-4.2 on 10.5 intel by following the README.LLVM

Rajkishore Barik <rb5 at rice.edu> writes: > I am trying to use the new LLVM-2.7 release in Xcode for my analysis > and development. > However, I do not see the top level Xcode directory as in LLVM-2.6. > Can someone tell me how > to develop on top of LLVM-2.7 using Xcode? Try using cmake: http://www.llvm.org/docs/CMake.html

Slightly off-topic, but I imagine this crowd must have some experience using Xcode 4 for projects linking to LLVM. I've actually started using Xcode 4 as an IDE for C/C++ development thanks to the vastly improved code analysis-based tools it's inherited largely thanks to LLVM. But, ironically, I am particularly struggling to get the tools to parse and analyze LLVM (as a client, not for

https://bugzilla.samba.org/show_bug.cgi?id=13044 Bug ID: 13044 Summary: On macOS 10.12.6 with the new Xcode 9, `make check` is full of failures Product: rsync Version: 3.1.2 Hardware: x86 OS: Mac OS X Status: NEW Severity: regression Priority: P5 Component: core

On 2010-07-21, at 2:24 AM, Brian Willoughby <brianw at sounds.wa.com> wrote: > The flac sources are distributed in a configuration that is designed > primarily for building from the command-line. I seem to recall that > there might have been an Xcode project in there at some point, but > if there was, it never worked well. In all honesty, I may be > getting

On Wed, Nov 14, 2012 at 11:18 PM, Jeffrey Walton <noloader at gmail.com> wrote: > Hi All, > > Please forgive me if this is the wrong group. I did not see a > llvm-user group (). The User Guide also lacked a topic > (http://llvm.org/docs/userguides.html#userguides). > > I am an Xcode user. I want to set a breakpoint on malloc_error_break > all the time (it makes no