search for: llvmexports

Hi, Myself and a colleague of mine are trying to use LLVM's exported targets [1] on trunk and I've noticed that the generated CMake files (LLVMConfig.cmake and LLVMExport.cmake) are broken when trying to use Visual Studio 2015 (using CMake 3.2.1). ## Broken target properties in LLVMExports.cmake LLVM itself builds fine but when our project tries to do ``find_package(LLVM)`` we get the following error message (see [2] for context). ``` -- Looking for LLVM CMake Warning (dev) at C:/Users/me/Documents/halide/llvm-build/share/llvm/cmake/LLVMExports.cmake:232 (set_target_properties):...

On 06/18/2015 06:46 PM, Dan Liew wrote: >> The issue is the that that generated LLVMExports.cmake file has this in it >> INTERFACE_LINK_LIBRARIES "LLVMObject;LLVMSupport;C:\Program Files (x86)\Microsoft Visual Studio 14.0\DIA SDK\lib\diaguids.lib" > > Hmm actually this might be a bug in the > ``/lib/DebugInfo/PDB/CMakeLists.txt`` file. CC'ing Zach Turner see...

...e be installed there? It's not necessary for CMake to be installed when building with the Autoconf/Makefile build system. If you look in the build directory after a build has been performed you should see in cmake/modules ``` LLVMBuildExports.cmake LLVMConfig.cmake LLVMConfigVersion.cmake LLVMExports.cmake Makefile ```` The ``LLVMConfig.cmake`` and ``LLVMConfigExports.cmake`` file are generated by the build in this directory and are later installed (along with a bunch of other files). When I do a build of LLVM on Arch Linux and install it in the install directory there is a ``share/llvm/cmake...

Hi, I can't reproduce your issue on the LLVM 3.5 release branch or trunk it. Looking at your bug report I think your install is messed up ``` CMake Error at /usr/local/Cellar/llvm/HEAD/share/llvm/cmake/LLVMExports.cmake:6 (set_property): set_property could not find TARGET LLVMSupport. Perhaps it has not yet been created. Call Stack (most recent call first): /usr/local/share/llvm/cmake/LLVMConfig.cmake:50 (include) CMakeLists.txt:4 (find_package) ``` /usr/local/share/llvm/cmake/LLVMConfig.cmake se...

...le variable. I have sent a patch to llvm-commits to try to fix this [3]. The result of this mistake is that the CMake files end up containing absolute paths to the temporary tarball directory which means they cannot be imported by another project. Second, the LLVM CMake files (LLVMConfig.cmake and LLVMExports.cmake) are not relocatable (they contain absolute paths which are based on the install prefix). So even if the first issue is fixed we still have the problem that a user cannot simply extract the binary tarball to an arbitrary location their system and build the toy project against it. I think the...

...ke to be installed when building with the >> Autoconf/Makefile build system. If you look in the build directory >> after a build has been performed you should see in cmake/modules >> >> ``` >> LLVMBuildExports.cmake LLVMConfig.cmake LLVMConfigVersion.cmake >> LLVMExports.cmake Makefile >> ```` > > > I have these for the test-release build, but only in the *.obj directory, > not the install directory. Okay. So that means the files are being generated during the build but not installed for some reason >> The ``LLVMConfig.cmake`` and ``LLVMC...

...tre at debian.org> wrote: > Le 09/05/2016 à 07:34, Paweł Bylica a écrit : > > llvm-3.8-dev is broken: > > > > CMake Error at /usr/share/llvm-3.8/cmake/LLVMConfig.cmake:178 (include): > > include could not find load file: > > > > /usr/share/llvm/cmake/LLVMExports.cmake > Brad King helped me and it should be fixed in the next few days/weeks. > Will the fix be included in the next build? > > > > llvm-3.7-dev is ok. > > > > Why is it so error prone for so many years? > Because the migration from autotool to cmake wasn't...

...;> d/bin -DLLVM_LIBRARY_OUTPUT_INTDIR=/home/abuild/rpmbuild/BUILD/lldb-3.8.0/build/lib64 >>>> -DPYTHON_VERSION_MAJOR=2 -DPYTHON_VERSIO >>>> N_MINOR=7 -G Ninja .. >>>> >>>> [...] >>>> >>>> CMake Error at /usr/share/llvm/cmake/LLVMExports.cmake:1011 (message): >>>> The imported target "LLVMSupport" references the file >>>> >>>> "/usr/lib64/libLLVMSupport.a" >>> >>> Could you try appending ``-DLLVM_LINK_LLVM_DYLIB=ON`` to your CMake >>> invocat...

...te: > because my Linux distribution just upgraded to LLVM/Clang 3.5 and I > noticed that trying use find_package(LLVM ...) was broken :( AFAIK, that never worked in any version of LLVM not built by CMake before. That's why we taught cmake/modules/Makefile to generate LLVMConfig.cmake and LLVMExports.cmake. > What is happening is that none of the libraries are being added into > LLVMExports.cmake file when it is generated by ``cmake/modules/Makefile``. [snip] > One way to "fix" this is make sure LLVMConfigLibs is also set when > using --enable-shared as the attached patch...

...Le 09/05/2016 à 07:34, Paweł Bylica a écrit : > > llvm-3.8-dev is broken: > > > > CMake Error at /usr/share/llvm-3.8/cmake/LLVMConfig.cmake:178 > (include): > > include could not find load file: > > > > /usr/share/llvm/cmake/LLVMExports.cmake > Brad King helped me and it should be fixed in the next few days/weeks. > > > Will the fix be included in the next build? It should be included now. > > > > > > llvm-3.7-dev is ok. > > > > Why is it so error prone for so many ye...

llvm-3.8-dev is broken: CMake Error at /usr/share/llvm-3.8/cmake/LLVMConfig.cmake:178 (include): include could not find load file: /usr/share/llvm/cmake/LLVMExports.cmake llvm-3.7-dev is ok. Why is it so error prone for so many years? On Sun, May 8, 2016 at 11:31 PM Amaury SECHET via llvm-dev < llvm-dev at lists.llvm.org> wrote: > So, it turns out that the secret sauce to clone that thing is $ svn co > svn://anonscm.debian.org/pkg-llvm/ > __...

...-DLLDB_PATH_TO_CLANG_BUILD=/usr -DLLVM_RUNTIME_OUTPUT_INTDIR=/home/abuild/rpmbuild/BUILD/lldb-3.8.0/buil d/bin -DLLVM_LIBRARY_OUTPUT_INTDIR=/home/abuild/rpmbuild/BUILD/lldb-3.8.0/build/lib64 -DPYTHON_VERSION_MAJOR=2 -DPYTHON_VERSIO N_MINOR=7 -G Ninja .. [...] CMake Error at /usr/share/llvm/cmake/LLVMExports.cmake:1011 (message): The imported target "LLVMSupport" references the file "/usr/lib64/libLLVMSupport.a" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure...

Hello everyone I was just porting a project to build against the LLVM 9 apt packages and noticed that the issue I filed and explained during the release phase in https://llvm.org/PR43035 still persists: CMake Error at /usr/lib/llvm-9/lib/cmake/llvm/LLVMExports.cmake:1323 (message):   The imported target "yaml-bench" references the file      "/usr/lib/llvm-9/bin/yaml-bench"   but this file does not exist. Here's a minimal repro: https://travis-ci.org/weliveindetail/apt-llvm-9-dev-repro/builds/619590445#L204 Is anyone else seei...

...=/home/abuild/rpmbuild/BUILD/lldb-3.8.0/buil >> d/bin -DLLVM_LIBRARY_OUTPUT_INTDIR=/home/abuild/rpmbuild/BUILD/lldb-3.8.0/build/lib64 >> -DPYTHON_VERSION_MAJOR=2 -DPYTHON_VERSIO >> N_MINOR=7 -G Ninja .. >> >> [...] >> >> CMake Error at /usr/share/llvm/cmake/LLVMExports.cmake:1011 (message): >> The imported target "LLVMSupport" references the file >> >> "/usr/lib64/libLLVMSupport.a" > > Could you try appending ``-DLLVM_LINK_LLVM_DYLIB=ON`` to your CMake > invocation? It looks like lldb is using the ``llvm_add_...

Hi, I've taken a look at the binary tarballs for clang+llvm-3.6.2-rc1-* that have been uploaded and observed the following: * All uploaded tarballs include the generated CMake files apart from ``clang+llvm-3.6.2-rc1-x86_64-linux-gnu-ubuntu-14.04.tar.xz``. These files (share/llvm/cmake/*.cmake) are missing in this tarball. * Inside the Ubuntu tarball the directory is not consistently named

Hi all, I can't seem to get the simplest CMakeLists.txt file working from http://llvm.org/docs/CMake.html#embedding-llvm-in-your-project. Do any of the LLVM projects use `find_package(LLVM REQUIRED CONFIG)`? Should I just be using `llvm-config` directly? http://llvm.org/bugs/show_bug.cgi?id=20884 David

...lo everyone >> >> I was just porting a project to build against the LLVM 9 apt packages >> and noticed that the issue I filed and explained during the release >> phase in https://llvm.org/PR43035 still persists: >> >> CMake Error at /usr/lib/llvm-9/lib/cmake/llvm/LLVMExports.cmake:1323 >> (message): >> >>    The imported target "yaml-bench" references the file >> >>       "/usr/lib/llvm-9/bin/yaml-bench" >> >>    but this file does not exist. >> >> Here's a minimal repro: >> https://tra...

> On Jan 14, 2016, at 11:43 AM, Ismail Donmez <ismail at i10z.com> wrote: > > On Thu, Jan 14, 2016 at 9:31 PM, Chris Bieneman via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> On Jan 14, 2016, at 11:22 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >> >> On Jan 14, 2016, at 9:38

Hi Brenden, Thanks for the heads up. I don’t expect that to be a blocker for deprecating autoconf because autoconf doesn’t have an equivalent of LLVMExports.cmake. That said it is a real issue and I’ll track it with the other issues on this list, and I’ve added it as a dependency on the meta bug (PR15732) to make it easier to keep track of. Thanks, -Chris > On Jul 29, 2015, at 4:48 PM, Brenden Blanco <bblanco at gmail.com> wrote: > >...

...iew <dan at su-root.co.uk> wrote: > This is happening because the ``LLVMConfigLibs`` makefile variable is > empty when used in ``cmake/modules/Makefile``. It is normally set in > Makefile.rules . However if you build with --enable-shared this > variable doesn't get set and so LLVMExports.cmake isn't generated > correctly. > > @David: Were you also compiling this way? The last time, yes. I built with OS X Homebrew (http://brew.sh) and it looks like their formulas use --enable-shared by default, although there is an option to turn it off (https://github.com/Homebrew/ho...