similar to: Windows binaries and LLVM_INSTALL_TOOLCHAIN_ONLY

Hans Wennborg via llvm-dev <llvm-dev <at> lists.llvm.org> writes: > This comes up now and then. >  > Yes, the packages would be a lot bigger, but IIRC the problem is also > that we don't have a good way to build to build LLVM into a shared > library on Windows that's suitable for shipping. I don't remember the > details here; maybe Reid does. Some of the

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

I’m trying to figure out how to build compiler-rt 3.5.0 with Visual Studio 2013. In an autotools build or cmake on Linux, I believe putting the compiler-rt sources under llvm/projects is enough to build them automatically. Do I need to do anything specific to get the same with MSVC? I've tried setting -DLLVM_BUILD_EXTERNAL_COMPILER_RT either ON or OFF, but can't find any evidence of

LGTM. -Chris > On Feb 27, 2015, at 3:27 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote: > > 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 > +++

I discovered that I can hack around my particular problem by placing set_property(TARGET clang PROPERTY INTERFACE_LINK_LIBRARIES) at the end of tools/driver/CMakeLists.txt. I'd prefer to fix this properly though, of course. On 12/1/17, 4:18 PM, "llvm-dev on behalf of Shoaib Meenai via llvm-dev" <llvm-dev-bounces at lists.llvm.org on behalf of llvm-dev at lists.llvm.org>

The CrossCompile module is in a perpetual state of "when I get a chance...", and desperately needs some cleanup. The problem you are hitting is caused by setting CMAKE_SYSTEM_NAME. When you set that CMake sets a variable CMAKE_CROSS_COMPILING. That variable should only be set when your host OS doesn't match your target OS. Since LLVM needs to build host-capable tools there is some

I need to build libLLVM (individual static libraries are fine at the moment) using mingw-w64 cross compilers, i686-w64-mingw32-gcc and (separately) x86_64-w64-mingw32-gcc. I'd like this to work from both Linux and Cygwin build environments. With autotools, this worked fine: ../configure --host=i686-w64-mingw32 and that's it (with mingw32-gcc-c++ installed on Fedora 23, also works fine on

On Fri, Jul 24, 2015 at 12:05 PM, Nico Weber <thakis at chromium.org> wrote: > On Thu, Jul 16, 2015 at 8:08 AM, Nico Weber <thakis at chromium.org> wrote: > >> On Wed, Jul 15, 2015 at 10:45 AM, Russell Wallace < >> russell.wallace at gmail.com> wrote: >> >>> Basic test results on Windows 7, visual studio 2013 (64 bit): >>> >>>

On 02/17/2016 07:23 PM, Tony Kelman via llvm-dev wrote: > Richard Pennington via llvm-dev <llvm-dev <at> lists.llvm.org> writes: > >> I use ELLCC to cross compile all the tools for various Linux targets and >> for Windows. Yesterday, after updating the LLVM sources, I got the >> following error when cross building for MinGW: > I haven't seen this exact

On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: > Hi waldi, > > Are you planning to update the Xen package too 4.4 soon? Upstream have > released 4.4-rc6 and AIUI are planning to release the final version next > week (I've been out of the office for a bit, so I don't know the precise > state, but that was the last I heard). > > I would like to send patches

Hi waldi, Are you planning to update the Xen package too 4.4 soon? Upstream have released 4.4-rc6 and AIUI are planning to release the final version next week (I've been out of the office for a bit, so I don't know the precise state, but that was the last I heard). I would like to send patches to enable the build on ARM but this relies on 4.4. I'm happy to do the upgrade first and

On 14/02/2020 4:04 pm, Jean-Philippe Brucker wrote: > With the built-in topology description in place, x86 platforms can now > use the virtio-iommu. > > Signed-off-by: Jean-Philippe Brucker <jean-philippe at linaro.org> > --- > drivers/iommu/Kconfig | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/iommu/Kconfig

On 14/02/2020 4:04 pm, Jean-Philippe Brucker wrote: > With the built-in topology description in place, x86 platforms can now > use the virtio-iommu. > > Signed-off-by: Jean-Philippe Brucker <jean-philippe at linaro.org> > --- > drivers/iommu/Kconfig | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/iommu/Kconfig

Hello, while improving and extending support for dllexport/import I have noticed that the current way these are implemented is problematic and I would like some input on how to proceed. Currently dllexport/dllimport is treated as linkage type. This conflicts with inlined functions because there is no linkage for the combination of both. On first though, combining both doesn't make sense, but

Hi all, I am trying to use llvm-gcc to link shared libraries on windows/mingw32. When I try to link libraries that contain functions declared with __declspec(dllexport) someFunction(); I get the link error: Cannot export _someFunction: symbol not found Removing the declspec directive solves the problem, but this is not a very feasible solution for me. Using 'regular' gcc does not

Hi Nico, Reid, and Anton, I missed the discussion when I implemented dllexport/dllimport for our local tree. I essentially implemented your approach#1. I was trying to avoid the various external_linkage + some_attribute approaches because it seems that external_linkage would imply the external linkage without the dllimport/dllexport semantics, and there may be existing compiler codes that rely on

> I am trying to use llvm-gcc to link shared libraries on windows/mingw32. > When I try to link libraries that contain functions declared with >  __declspec(dllexport) someFunction(); > > I get the link error: > >  Cannot export _someFunction: symbol not found dllexport declspec should be put on the function definition, in this example there is nothing to export - dllexport

Hi, I recently switched over to using cmake to build my clang/LLVM based ELLCC cross development project (http://ellcc.org). I also recently updated to LLVM svn version 258915 from 258477. I use ELLCC to cross compile all the tools for various Linux targets and for Windows. Yesterday, after updating the LLVM sources, I got the following error when cross building for MinGW: [ 3%] Built

Hello. I was trying to compile https://github.com/llvm/llvm-project/tree/master/libunwind using: - MSVC - Clang I wasn't able to configure this project for using MSVC (directly or via clang-cl): >cmake -G Ninja -DLLVM_PATH="C:/Users/clang/llvm-project-10.0.1/llvm" -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX="C:\Users\clang\libunwind_llvm" ../libunwind --

If building a static library, marking symbols as dllexport causes them to be exported from the final executable. For example, run objdump -x opus_demo.exe on a --disabled-shared build and look for the export table; there should not be one in a normal Win32 .exe file, but when linking static libopus, the exe exports all of the opus_* public functions. Use the libtool-defined DLL_EXPORT flag to