Comments on: ToT Clang / LLVM in Xcode https://wadetregaskis.com/tot-clang-llvm-in-xcode/ Tue, 02 Jan 2024 04:33:18 +0000 hourly 1 By: Yuriy https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-508 Wed, 21 May 2014 15:38:55 +0000 http://blog.wadetregaskis.com/?p=2417#comment-508 Just thank you. I succeeded Mac OS 10.9 / XCode 5.1.1

]]> By: Nisim https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-330 Mon, 05 Aug 2013 13:24:41 +0000 http://blog.wadetregaskis.com/?p=2417#comment-330 for LLVM 3.3 release use the following:

https://web.archive.org/web/20140801003514/https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_33/final
https://web.archive.org/web/20140908133202/http://llvm.org/svn/llvm-project/cfe/tags/RELEASE_33/final/
https://github.com/llvm/llvm-project/tree/llvmorg-3.3.0/compiler-rt
https://github.com/llvm/llvm-project/tree/llvmorg-3.3.0/libcxx

]]> By: burt0n https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-272 Mon, 10 Jun 2013 08:13:42 +0000 http://blog.wadetregaskis.com/?p=2417#comment-272 XCode 4.6.2 (OS X 10.8.4) correctly recognizes my locally installed clang, but in case of errors it fails in displaying the error line(s). The only output available is ‘Command /usr/local/bin/clang failed with exit code 1’ along with the output resulting from the compilation attempt.

How can I instruct XCode so as to highlight the error line(s) as if I were using the built-in clang? Thanks.

]]> By: James Walker https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-149 Fri, 15 Mar 2013 22:26:29 +0000 http://blog.wadetregaskis.com/?p=2417#comment-149 Using libc++ and -fsanitize=undefined, i386 architecture, I get link errors on 4 missing symbols:


typeinfo for __cxxabiv1::__class_type_info
typeinfo for __cxxabiv1::__si_class_type_info
typeinfo for __cxxabiv1::__vmi_class_type_info
typeinfo for std::type_info

Any idea what I’m missing?

]]> By: Brad https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-148 Thu, 14 Mar 2013 19:45:45 +0000 http://blog.wadetregaskis.com/?p=2417#comment-148 In reply to Jean-Daniel.

Thanks @Jean-Daniel — yes I eventually figured that out, and got everything to work. Forgot to make a note of it here.

]]> By: Jean-Daniel https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-147 Thu, 14 Mar 2013 18:28:06 +0000 http://blog.wadetregaskis.com/?p=2417#comment-147 In reply to Brad.

@Brad: You need to also include libc++ headers in your clang build.

Before building just do an other checkout in projects (next to compiler-rt):

svn co https://web.archive.org/web/20140726061724/http://llvm.org/svn/llvm-project/libcxx/trunk/ libcxx

The “make install” step with then copy the libcxx header where needed.

]]> By: Brad https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-131 Mon, 25 Feb 2013 14:56:50 +0000 http://blog.wadetregaskis.com/?p=2417#comment-131 PS. The library headers that are missing are for cmath, complex, and iostream (the angular brackets were edited out in my first comment).

]]> By: Brad https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-130 Mon, 25 Feb 2013 13:41:32 +0000 http://blog.wadetregaskis.com/?p=2417#comment-130 Setting CC=/path/to/clang in an .xcconfig file works well for me too, but clang (llvm 3.3 svn) isn’t able to find the , , or library headers in my code. [This is true for the released version of clang (llvm 3.2) as well.] The Apple-supplied version of clang (Xcode installed command-line tool), by contrast, finds the header files. (I’m running OS X 10.8.2).

Does anyone know how to show clang where these header files are located?

]]> By: Sean https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-53 Fri, 31 Aug 2012 20:16:59 +0000 http://blog.wadetregaskis.com/?p=2417#comment-53 Gus’ suggestion works great for me. I set CC=/path/to/clang in my .xcconfig file and presto! I still have to copy the ‘arc’ folder as the article describes. After that I got other link errors though:

Undefined symbols for architecture x86_64:
“_llvm_gcda_emit_arcs”, referenced from:
“_llvm_gcda_emit_function”, referenced from:
“_llvm_gcda_end_file”, referenced from:
“_llvm_gcda_start_file”, referenced from:

Which I fixed by temporarily disabling code coverage (GCC_INSTRUMENT_PROGRAM_FLOW_ARCS, GCC_GENERATE_TEST_COVERAGE_FILES).

]]> By: JayZ https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-45 Sun, 08 Jul 2012 16:55:59 +0000 http://blog.wadetregaskis.com/?p=2417#comment-45 It seems I can’t get this to work… I followed your instructions and edited only the paths ans nothing else (for troubleshooting) in the .xcspec file to “/Users/JayZ/usr/bin/clang” and, since I am using XCode 4.2, copied the xcplugin to /Developer/Library/Xcode/Plug-ins. Unfortunately I fail to be able to choose the compiler within XCode. I am using Snow Leopard. Any help appreciated ;)

]]> By: Flash Sheridan https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-36 Thu, 24 May 2012 19:25:59 +0000 http://blog.wadetregaskis.com/?p=2417#comment-36 You can also try to use a different version of the static analyzer via the Python script set-xcode-analyzer bundled with the releases at https://clang-analyzer.llvm.org/installation. But note that this may depend on the version(s) of Python you’ve got installed: https://bugs.llvm.org/show_bug.cgi?id=11661

]]> By: Gus Mueller https://wadetregaskis.com/tot-clang-llvm-in-xcode/#comment-17 Sun, 13 May 2012 03:56:42 +0000 http://blog.wadetregaskis.com/?p=2417#comment-17 Just as an aside, I’ve found that adding a user defined setting of “CC” equal to /opt/bin/clang is preferable to using the plugin. Just change your build script to use:
./configure –prefix=/opt –enable-optimized

You’ll even be able to use the latest static analyzer as well.

]]>