similar to: [LLVMdev] automatic discovery of new CMake projects

Sorry, attached the wrong patch last time. ________________________________ From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Viktar Zviarovich Sent: 04 March 2009 14:19 To: llvmdev at cs.uiuc.edu Subject: [LLVMdev] automatic discovery of new CMake projects Hi all, The suggested patch enables addition of all subdirectories of llvm/projects to

"Viktar Zviarovich" <Viktar.Zviarovich at brunel.ac.uk> writes: > The suggested patch enables addition of all subdirectories of > llvm/projects to CMake build. > > It somewhat simplifies the process of creating new projects that use > CMake instead of make, eliminating the need of editing > llvm/CMakeLists.txt and llvm/projects/CMakeLists.txt. This is not

Hi Óscar, Thank you for the reply. I indeed got an impression (may be incorrect) that projects/ directory is intended for users' projects that are not committed to LLVM repository. Otherwise, of course, the patch doesn't make much sense. Anyway, I've added a comment about the need of explicit CMake invocation to projects/CMakeLists.txt. Thanks, Victor -----Original Message-----

Dear llvm-dev, First of all I'd like to thank LLVM developers for doing a great job! I am trying to use LLVM libraries on Windows using Visual Studio environment and everything works very smoothly until it comes to the execution engine. I construct a module and obtain a pointer to the function in it using ExecutionEngine::getPointerToFunction but calling this function (after appropriate

"Viktar Zviarovich" <Viktar.Zviarovich at brunel.ac.uk> writes: [snip] > The function I am trying to call is trivial (took it from the tutorial > just for testing purposes) and has C calling conventions. The > execution engine returned by ExecutionEngine::create is Interpreter. > > Am I doing something wrong or is it a bug? Are you using CMake for generating the

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):   Cannot run debuginfo-tests without python 3 installed python3

On 19 June 2015 at 15:57, Mehdi Amini <mehdi.amini at apple.com> wrote: > Hi, > > If you just want to *link* to LLVM, it is not clear to me why you are not > just relying on LLVM being built separately and have your project CMake > pointing to the llvm build directory and using llvm-config to populate the > linker argument? > > Best, > — > Mehdi > This is

Dear All, Thanks for the feedback. To clarify, this is for LLVM-related projects that are linking against the LLVM libraries. The feature for keeping our source code in arbitrary locations isn't something we need. If we can just drop our source code into llvm/projects (or some other designated LLVM subdirectory) and write LLVM-esque CMake files, that should be enough for projects that

This way, an LLVM compiled after setting GCC_INSTALL_PREFIX will work correctly if you don't want to install LLVM into the GCC_INSTALL_PREFIX. --- CMakeLists.txt | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index 9ec3e33..c85a028 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -450,7 +450,12 @@ if (APPLE)

On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/19/2020 09:05 PM, Sedat Dilek wrote: > > Hi Tom, > > > > thanks and congrats for LLVM 10.0.1-rc1 release. > > > > [1] shows 2 assets. > > 10.0.0 RCs had a lot of more assets. > > I am missing the llvm-project-10.0.1rc1.tar.xz tarball. > > > > Will

----- Original Message ----- > From: "Eric Christopher" <echristo at gmail.com> > To: "John Criswell" <jtcriswel at gmail.com>, LLVMdev at cs.uiuc.edu, "Chris Bieneman" <beanz at apple.com> > Sent: Thursday, June 18, 2015 7:14:06 PM > Subject: Re: [LLVMdev] Long-Term Support for LLVM Projects Extension to Build System? > > > On

The behavior of automatically detecting libraries installed in the same prefix feels like magic to me anyway. Perhaps it would be better to have project-level variables for specifying the path to them individually? The default value for them could remain as origin/../lib which would keep from breaking things. On Thu May 29 2014 at 7:06:17 PM, Chandler Carruth <chandlerc at google.com>

Signed-off-by: Sedat Dilek <sedat.dilek at gmail.com> --- CMakeLists.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index ed7aeb026f5d..60fe427e456e 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -66,7 +66,7 @@ set(LLVM_VERSION_PATCH 0) set(LLVM_VERSION_SUFFIX svn) if (NOT PACKAGE_VERSION) - set(PACKAGE_VERSION

Hi, As it stands, I cannot build nor test compiler-rt. I downloaded the latest sources from svn (http://llvm.org/svn/llvm-project/compiler-rt/trunk) and ran cmake ../../Source/compiler-rt -G"MinGW Makefiles" and got the following error: ... -- Detecting CXX compiler ABI info - done CMake Error at CMakeLists.txt:10 (include): include could not find load file: LLVMParseArguments

Óscar Fuentes wrote: > "Anton Korobeynikov" <asl at math.spbu.ru> writes: > > >>> at all, it would be great if you reflect your changes on the file list >>> inside the corresponding CMakeLists.txt when you add, remove or rename >>> a .cpp file. >>> >> Isn't is possible for cmake just to glob everything in the

Hi Nick Thanks for you reply. CMAKE is very new to me. I complied using GNU WIN32 and got those errors. Is it possible to compile it using GNU WIN 32 and anything need to be modified? I managed to compile the run time library on a mac machine. Yafan On Fri, Apr 22, 2011 at 5:04 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > yafan zhao wrote: > >> Hi All >> Thanks for

Hi Tom, thanks and congrats for LLVM 10.0.1-rc1 release. [1] shows 2 assets. 10.0.0 RCs had a lot of more assets. I am missing the llvm-project-10.0.1rc1.tar.xz tarball. Will you provide them later or is there a new development/workflow decision I do not know of? BTW, the source zip and tar.gz tarballs show no sizes. I am using Mobile LTE/UMTS to download stuff from the Internet. For now I

On Wed, May 20, 2020 at 11:12 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/20/2020 09:53 AM, Sedat Dilek wrote: > > On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > >> > >> On 05/19/2020 09:05 PM, Sedat Dilek wrote: > >>> Hi Tom, > >>> > >>> thanks and congrats for LLVM

This isn't meant to be a sample, but I can share with you the cmake files I use for my compiler. It builds in both windows user MSVC, and linux using G++, but should work with MinGW. the structure is src/ CMakeLists.txt # root make file front/ CMakeLists.txt # library middle/ CMakeLists.txt # library back/ CMakeLists.txt # library npp/ CMakeLists.txt # executable

Hi Dean, For me the build is still broken: -- Builtin supported architectures: i386;x86_64;x86_64h CMake Error at projects/compiler-rt/lib/xray/tests/CMakeLists.txt:21 (add_library): add_library cannot create target "RTXRay.test.osx" because another target with the same name already exists. The existing target is a static library created in source directory