similar to: tooling libraries missing in Windows download

Hello list! So I'm wondering if there is a will to ship a DLL with the C API exported? LLVM currently ships with LTO.dll which has some C api functions exported, made from the export file tools/lto/lto.exports, so it would not be the first DLL LLVM shipped. Currently I (and the users of my project[1]) are building it ourselves using this script[2] derived from the LLVMSharp script[3]. Which

We already half-have this, the LLVM_BUILD_LLVM_C_DYLIB cmake option builds a shared object which exports the llvm-c interface but it only works on Darwin. tools/llvm-shlib/CMakeLists.txt is where how this is done is defined, and it looks like it does it by: * build LLVM.so * use nm+awk+sed to pick out the symbols starting with LLVM * build LLVM-C.so using a -reexport_library linker option

The following is an older commandline i used. Have a more recent one at home. But basically you can write it as batch and trigger it within a target during the build(never got targets into correct order, i am a cmake noob) So for reference, i'll post this one and look for the recent one at home(if that didn't go down with my recent hdd crash): cmd /Q /V:ON /c "for /F

On Wed, Dec 23, 2015 at 9:38 PM, Aaron Ballman <aaron at aaronballman.com> wrote: > On Wed, Dec 23, 2015 at 3:28 PM, Reid Kleckner <rnk at google.com> wrote: >> On Wed, Dec 23, 2015 at 11:25 AM, Aaron Ballman via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> >>> On Wed, Dec 23, 2015 at 1:55 PM, Jakob Bornecrantz <wallbraker at

Made a bit of headway here: https://reviews.llvm.org/D35077 Cheers, Jakob. On Thu, Apr 6, 2017 at 2:34 PM, Alexander Benikowski <sebal007 at googlemail.com> wrote: > Maybe someone can use this as a startingpoint to add the windows-specific > commandblock which is triggered instead of the Darwin one together with a > proper setup of targets to have the libs build before. > >

r257499 On Sun, Jan 10, 2016 at 1:23 PM, Jakob Bornecrantz <wallbraker at gmail.com> wrote: > On Thu, Dec 24, 2015 at 1:28 AM, Jakob Bornecrantz <wallbraker at gmail.com> > wrote: > > On Wed, Dec 23, 2015 at 9:38 PM, Aaron Ballman <aaron at aaronballman.com> > wrote: > >> On Wed, Dec 23, 2015 at 3:28 PM, Reid Kleckner <rnk at google.com> wrote:

Thanks for starting! Btw here is my CMD version: cmd /Q /V:ON /c "for /F "tokens=4" %l in ('dir llvm*.lib') do (for /F "tokens=2" %e in ('dumpbin /linkermember:1 %l ^| findstr "_LLVM"') do (set symbolname=%e & echo !symbolname:~1!))" You run it in the directory with all the llvm*.lib (yes the ThinLTO is excluded in this example but can

On Wed, Dec 23, 2015 at 11:25 AM, Aaron Ballman via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Wed, Dec 23, 2015 at 1:55 PM, Jakob Bornecrantz <wallbraker at gmail.com> > wrote: > > On Wed, Dec 23, 2015 at 5:49 PM, Aaron Ballman <aaron at aaronballman.com> > wrote: > >> On Wed, Dec 23, 2015 at 11:29 AM, Jakob Bornecrantz via llvm-dev > >>

Thanks! That should get me on the right track. Direct reply was accidental. Thanks for putting me back on the list :-) I'll repost with details once I've got it working. On Mon, Feb 27, 2017 at 10:00 PM, Tim Northover <t.p.northover at gmail.com> wrote: > Hi John, > > [Adding llvm-dev again; best to keep these things in the open so they > show up in future searches].

I am sorry, just noticed i repeated myself :( 2017-07-10 15:20 GMT+02:00 Alexander Benikowski <sebal007 at googlemail.com>: > Thanks for starting! > Btw here is my CMD version: > > cmd /Q /V:ON /c "for /F "tokens=4" %l in ('dir llvm*.lib') do (for /F > "tokens=2" %e in ('dumpbin /linkermember:1 %l ^| findstr "_LLVM"') do

I'm trying to build LLVM on Windows 10 for x86_64. The cmake cmdline I used is c:\cmake-3.8.0-rc1-win64-x64\bin\cmake.exe -DLLVM_TARGETS_TO_BUILD=x86_64 -G "Visual Studio 14" . And this ultimately gives me: llvm-build: error: invalid target to enable: 'x86_64' (not in project) The source I'm trying to build is the llvm-3.8.0.src.tar.xz I got from

On Wed, Aug 29, 2018 at 10:14 AM, Hans Wennborg <hans at chromium.org> wrote: > On Wed, Aug 29, 2018 at 9:45 AM, Sedat Dilek via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi, >> >> for filing a GCC v8.2.0 bug in Debian/buster AMD64 the Debian/GCC >> mainatiners want two things... >> >> [ FULL CMAKE LINE ] >> >> How do I

Hi, I have not sent yet any bug-reports to llvm-dev but I am seeing this build-failure: ... [574/3685] Building CXX object lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o FAILED: lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o /usr/bin/g++-8 -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS

On Tue, Aug 28, 2018 at 10:26 AM, Sedat Dilek via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Mon, Aug 27, 2018 at 6:09 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >> Hi, >> >> I have not sent yet any bug-reports to llvm-dev but I am seeing this >> build-failure: >> >> ... >> [574/3685] Building CXX object >>

On 28.08.2018 13:55, Sedat Dilek wrote: > On Tue, Aug 28, 2018 at 10:59 AM, Hans Wennborg <hans at chromium.org> wrote: >> On Tue, Aug 28, 2018 at 10:26 AM, Sedat Dilek via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>> On Mon, Aug 27, 2018 at 6:09 PM, Sedat Dilek <sedat.dilek at gmail.com> wrote: >>>> Hi, >>>> >>>>

On Wed, Aug 29, 2018 at 9:29 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > On Wed, Aug 29, 2018 at 7:51 AM, Matthias Klose <doko at debian.org> wrote: >> On 28.08.2018 13:55, Sedat Dilek wrote: >>> On Tue, Aug 28, 2018 at 10:59 AM, Hans Wennborg <hans at chromium.org> wrote: >>>> On Tue, Aug 28, 2018 at 10:26 AM, Sedat Dilek via llvm-dev

Hi, for filing a GCC v8.2.0 bug in Debian/buster AMD64 the Debian/GCC mainatiners want two things... [ FULL CMAKE LINE ] How do I configure this in the LLVM/Clang build? Can I set an option of cmake? [ PREPROCESSED SOURCE FILES ] How and where do I get the preprocessed source? Do I need to set options for this in my build-script? My build-script is attached. Thanks in advance. Regards, -

FWIW, I've got a powershell script that builds an exports.def file for recognizable C functions. You could adapt it to Python and make it part of the official build if the LLVM community thinks it will be beneficial to have libLLVM.dll The script is located here: https://github.com/mjsabby/LLVMSharp/blob/master/GenLLVMDLL.ps1 On Wed, Apr 1, 2015 at 9:03 AM, Reid Kleckner <rnk at

I'm building on Windows x64 using cmake, Ninja and VS 2013 express on Windows 7. So I have been using the LLVMSharp method on getting a usable loadable LLVM.dll[1][2]. This have worked out of the box before so it is a regression, I tracked it down to commit r250501. That commit breaks this commit, other users have also run into this specific problem[3][4]. I tried looking into the

Upon reading http://llvm.org/docs/GettingStarted.html it says I can build shared libs, but when going to the CMake doc ( http://llvm.org/docs/CMake.html) it says Shared libraries are not supported on Windows and not recommended for other OSes. Is there a reason why? At least for on Windows. -------------- next part -------------- An HTML attachment was scrubbed... URL: