search for: dllvm_enable_projects

...020 11:27 AM, Steven Wu via llvm-dev wrote: > I like the proposal but I would like to go even further. If we are going to create a top level CMake file, we should just go ahead and eliminate all the standalone build configuration. The standalone build should just be `cmake <monorepo-root> -DLLVM_ENABLE_PROJECTS=standalone-project ...`. That means less build configuration to maintain which is always good. > Eliminating stand-alone builds would be an inconvenience for us in Fedora, since this is how we build LLVM packages. However, I think we may have different definitions of what a stand-alone build i...

...missing libraries are defined in files under the ‘clang’ directory. The llvm_project clone has the following structure: llvm-project llvm clang (others) Everything under ‘llvm’ is properly compiled with no issues, however what is under ‘clang’ fails to compile (with linker errors) even if -DLLVM_ENABLE_PROJECTS=“clang” is specified. I suspect now that there may be some kind of bug in the llvm project that prevents this to work properly, or maybe something else needs to be done to get clang compiled on xcode. I also suspect that this may pass unnoticed when using ninja because it simply uses it’s own way...

...i 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 project is enabled’. However, the ‘clang’ schema, and anything related with clang, is completely missing in the generated xcode project, so clang can’t be compiled. This is the full command line that I used from the 'llvm...

...monorepo layout at all, but in any case, it does describe how to do the entire process by hand, so I went for that. Here are my steps: * Built a release version of LLVM/Clang/LLD/compiler-rt on version 9.0.0-rc3 * Built an instrumented clang with the following config: cmake -G Ninja ../llvm \ -DLLVM_ENABLE_PROJECTS='clang;compiler-rt' \ -DLLVM_TARGETS_TO_BUILD=X86 \ -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \ -DCMAKE_CXX_COMPILER=/path/to/release_build/bin/clang++ \ -DCMAKE_C_COMPILER=/path/to/release_build/bin/clang \ -DLLVM_USE_LINKER=/path/to/release_build/bin/ld.lld \ -DLLVM_CCACHE_BUILD=ON \...

...r/local all the projects under llvm except llgo yesterday. The three files you noted are in > ../llvm-project/build/lib > I do not have a llvm-project/build/Debug directory. > Xubuntu 19.04. llvm downloaded from github on 6/18 using instructions from the page you note. > cmake -G Ninja -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;compiler-rt;debuginfo-tests;libclc;libcxx;libcxxabi;libunwind;lld;lldb;llvm;openmp;parallel-libs;polly;pstl" -DLLVM_USE_LINKER=lld -DCMAKE_BUILD_TYPE="Release" ../llvm > Installed additional packages as needed. > Neil > On 7/5/19 6:46 AM, Joan L...

...nvestigate further. >>> >>> Should this have just worked out of the box? >> >> Yes, can you post your cmake invocation, I’ll investigate. > > Sorry, I should have done that initially. I copied it from the website: > > cmake -GNinja ../llvm-project/llvm -DLLVM_ENABLE_PROJECTS="clang;libcxx;compiler-rt” It builds for me right now on OSX (running `ninja check-all` right now), can you `git pull`, try again from a clean build dir, and send me the trace (including the hash you’re on and your OS / platform as well). Thanks, Mehdi

...e ‘clang’ directory. > > The llvm_project clone has the following structure: > > llvm-project > llvm > clang > (others) > > Everything under ‘llvm’ is properly compiled with no issues, however what > is under ‘clang’ fails to compile (with linker errors) even if > -DLLVM_ENABLE_PROJECTS=“clang” is specified. > > I suspect now that there may be some kind of bug in the llvm project that > prevents this to work properly, or maybe something else needs to be done to > get clang compiled on xcode. I also suspect that this may pass unnoticed > when using ninja because it s...

...lvm_project clone has the following structure: >> >> llvm-project >> llvm >> clang >> (others) >> >> Everything under ‘llvm’ is properly compiled with no issues, however >> what is under ‘clang’ fails to compile (with linker errors) even if >> -DLLVM_ENABLE_PROJECTS=“clang” is specified. >> >> I suspect now that there may be some kind of bug in the llvm project that >> prevents this to work properly, or maybe something else needs to be done to >> get clang compiled on xcode. I also suspect that this may pass unnoticed >> when usin...

...he entire process by hand, so I went for that. Here are >> my steps: >> >> * Built a release version of LLVM/Clang/LLD/compiler-rt on version >> 9.0.0-rc3 >> >> * Built an instrumented clang with the following config: >> cmake -G Ninja ../llvm \ >> -DLLVM_ENABLE_PROJECTS='clang;compiler-rt' \ >> -DLLVM_TARGETS_TO_BUILD=X86 \ >> -DCMAKE_EXPORT_COMPILE_COMMANDS=ON \ >> -DCMAKE_CXX_COMPILER=/path/to/release_build/bin/clang++ \ >> -DCMAKE_C_COMPILER=/path/to/release_build/bin/clang \ >> -DLLVM_USE_LINKER=/path/to/release_...

cmake ../llvm/ -G "Unix Makefiles" -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_INSTALL_PREFIX=../install -DLLVM_TARGETS_TO_BUILD="XXX" -DLLVM_ENABLE_PROJECTS='lld;clang;' ________________________________ From: Hans Wennborg <hans at chromium.org> Sent: Thursday, March 21, 2019 2:21 AM To: Josh Sharp Cc: Brian Cain; via llvm-dev Subject: Re: [llvm-dev] LLVM 8.0.0 Release Clang should be in the same folder. Can you share the full commands y...

where should the file build_llvm_package.bat be placed and how should the build_llvm_package.bat be called? or is there a another way to do a two stage build of the llvm project on windows starting with using visual studio 2017 community. -------------- next part -------------- An HTML attachment was scrubbed... URL:

...link with a dynamically loaded plugin? How can I use the EngineBuilder in my plugin with proper symbol resolution? For reproductivity: cmake -G "Sublime Text 2 - Ninja" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DLLVM_EXPORT_SYMBOLS_FOR_PLUGINS=ON -DLLVM_BUILD_TESTS=ON -DLLVM_BUILD_EXAMPLES=ON -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra" -DLLVM_TOOL_CLANG_BUILD=ON -DLLVM_TOOL_CLANG_TOOLS_EXTRA=ON -DLLVM_OPTIMIZED_TABLEGEN=ON -DCLANG_BUILD_EXAMPLES=ON -DCLANG_PLUGIN_SUPPORT=ON Hope someone can help me out. Viktor -------------- next part -------------- An HTML attachment was scrubbed... URL: <...

...structure: >>> >>> llvm-project >>> llvm >>> clang >>> (others) >>> >>> Everything under ‘llvm’ is properly compiled with no issues, however >>> what is under ‘clang’ fails to compile (with linker errors) even if >>> -DLLVM_ENABLE_PROJECTS=“clang” is specified. >>> >>> I suspect now that there may be some kind of bug in the llvm project >>> that prevents this to work properly, or maybe something else needs to be >>> done to get clang compiled on xcode. I also suspect that this may pass >>>...

...n Clang in the system and it does not produce this issue. When I search for this issue on Google, it seems to be relevant to “RTTI”. But as I know LLVM is built by default -fno-rtti. I also explicitly turned off it. Here is my cmake command: $ cmake -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_RTTI=OFF -DLLVM_ENABLE_PROJECTS=clang -G "Unix Makefiles" ../llvm Any thought? Best, - Kihong > On Jun 28, 2019, at 5:39 AM, Tim Northover <t.p.northover at gmail.com> wrote: > > Hi Kihong, > > On Fri, 28 Jun 2019 at 05:58, Kihong Heo via llvm-dev > <llvm-dev at lists.llvm.org> wrote:...

Hi Team, I have checked out the clang and llvm source code and built the executables using the visual studio 2015 community edition. I am using Windows as my platform. However I see that there are some test cases under the clang test folder in the LLVM.sln. Eg AstMatcherTest,ASTTests etc. I see that these tests make use of the Google test framework. In my visual studio I have

...work with the LLVM repo if it is desired. 2016-09-08 21:49 GMT+02:00 Renato Golin via llvm-dev < llvm-dev at lists.llvm.org>: > On 8 September 2016 at 19:37, Mehdi Amini via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > I'd expect a cmake shortcut cmake > > -DLLVM_ENABLE_PROjECTS=clang,libcxx,compiler-rt > > Hey, I like this idea! > > In that case, we don't need the directories in any particular > location, as CMake would be able to find and link any place *we* want > to put them in (in tree, flat out) and pull out their CMake files. > > This wou...

...ts.txt whose sole job is to include subprojects. We could also place basic LLVM-wide things like the check for the minimum CMake version there. More specifically, I would like to be able to do: $ cd <monorepo-root> $ mkdir build $ (cd build && cmake <monorepo-root> -DLLVM_ENABLE_PROJECTS="<projects-to-enable>") Pretty much the only difference with today is that you'd use `cmake <monorepo-root>` instead of `cmake <monorepo-root>/llvm`. Like I said, this is a problem for the runtime projects, but I'm not sure about other projects. For the runtime...

cmake -G Ninja -DLLVM_ENABLE_PROJECTS="debuginfo-tests" -DLLVM_USE_LINKER=lld -DCMAKE_BUILD_TYPE="Release" -DLLVM_TARGETS_TO_BUILD=X86 -Wno-dev ../llvm &> ../../cmake.log in cmake.log -- Targeting X86 CMake Error at /home/nnelson/Documents/llvm-project/debuginfo-tests/CMakeLists.txt:30 (message):   Cann...

...-DCMAKE_BUILD_TYPE=Release -DLLVM_OPTIMIZED_TABLEGEN=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_ENABLE_LIBXML2=OFF -DCMAKE_C_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" -DCMAKE_CXX_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" -DCMAKE_LINKER="%VS2019%/bin/HostX64/x64/link.EXE" -DLLVM_ENABLE_PROJECTS="llvm;clang;lld;clang-tools-extra;compiler-rt;mlir;polly" -DLLVM_ENABLE_PDB=ON -DLLVM_POLLY_LINK_INTO_TOOLS=ON These tests fail with Clang 9.0.1: Failing Tests (3): Clang Tools :: clang-tidy/checkers/cert-mem57-cpp-cpp17.cpp Clang Tools :: clang-tidy/checkers/performance-noexcep...