similar to: [PATCH] [CMAKE] Allow a toolchain file for the host when cross-compiling

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

I'm an idiot and sent to llvm-commits instead of llvm-dev. Fixing. On 10/17/17, 5:09 PM, "llvm-commits on behalf of Shoaib Meenai via llvm-commits" <llvm-commits-bounces at lists.llvm.org on behalf of llvm-commits at lists.llvm.org> wrote: Hi all (CC beanz for cmake advice), I'm running into a cmake problem when I try to cross-compile a

This will be used by Clang to show full build information when LLVM_APPEND_VC_REV is enabled and LLVM/Clang are built from Git. Also try to figure-out repository URL and revision from Git mirror parsing git-svn-id: footer from last commit (if present). --- cmake/modules/VersionFromVCS.cmake | 55 ++++++++++++++++++++++++++++---------- 1 file changed, 41 insertions(+), 14 deletions(-) diff --git

> > Replicating ExternalProject would be a lot of work... > One approach commonly used with CMake modules that change frequently upstream is for the project to keep a local copy and have a check in place to use CMake's version if new enough. For instance, in llvm's source tree: cmake/modules/ExternalProject.cmake: if(CMAKE_VERSION VERSION_LESS "3.5.1")

Hi Rafael, I looked at the code which you pushed a while ago to check for the gold linker. Code below: execute_process( COMMAND ${CMAKE_C_COMPILER} -Wl,--version OUTPUT_VARIABLE stdout ERROR_QUIET) if("${stdout}" MATCHES "GNU gold") set(LLVM_LINKER_IS_GOLD ON) endif() I was trying to build runtime libraries (compiler-rt)

I have just committed support to llvm-ar for creating thin archives. The idea of thin archives is that they contain just the symbol table and the path to find the original .o files. By locally making thin archives the default I was able to build llvm+lld+clang with them. The total size of the .a files goes from 181,658,164 to 7,116,900 bytes. Is there any way to do that with cmake without having

On Tue Nov 17, 2020 at 10:35 PM GMT, Michael Kruse wrote: > Am Di., 17. Nov. 2020 um 12:46 Uhr schrieb Luke Drummond via llvm-dev > <llvm-dev at lists.llvm.org>: > > > > On Tue Nov 17, 2020 at 6:37 PM GMT, Min-Yih Hsu wrote: > > > > > Just trying to understand: Are you suggesting a way to have a “-O0” > > > build without all the debug information?

On 17 July 2015 at 07:19, Brad King <brad.king at kitware.com> wrote: > On 07/15/2015 09:00 PM, Rafael Espíndola wrote: >> I have just committed support to llvm-ar for creating thin archives. >> The idea of thin archives is that they contain just the symbol table >> and the path to find the original .o files. > > Neat! Is this expected to be used only for

LLVM currently has CMake code to try to detect the various options needed to compile with C++11 support that has been around since prior to the CMake version bump. One of the nicer features that came with the newer required CMake version is that very thing. Rather than try to discern this yourself CMake has the CXX_STANDARD and CXX_STANDARD_REQUIRED target properties. If set appropriately on a

On 20 July 2015 at 10:53, Brad King <brad.king at kitware.com> wrote: > On 07/20/2015 10:48 AM, Rafael Espíndola wrote: >>>> Setting CMAKE_CXX_CREATE_STATIC_LIBRARY works on OS X and linux, but >>>> on windows I still see a call to "lld-link2 /lib..." when >>>> CMAKE_CXX_CREATE_STATIC_LIBRARY is set to use llvm-lib. >> >> I was

> CMake has undocumented variables set by the Modules/Platform/* > files to specify the rules for creating archives. These are: > > CMAKE_<LANG>_ARCHIVE_{CREATE,APPEND,FINISH} > > for creating, appending to, and finishing an archive. For > tools/platforms that do not support separate steps we also > have: > > CMAKE_<LANG>_CREATE_STATIC_LIBRARY Setting

Most of the comments I have are actually very well captured by Chandler's email, so I'm not going to pile on. I do have a few things to add. Renato, in your most recent email you comment about differentiating *stable* vs random versions of CMake built from source. I believe as a community our recommendation should be that people download CMake sources from https://CMake.org/download/

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

Hello everyone. I thought I had everything configured correctly but it seems not. I've got two servers. One is the AD DC and another that has been joined to the domain. This is the output I get first from the AD DC when I do a getent: root at dc1:/etc# getent group 'Domain Admins' AD\domain admins:x:3000004: root at dc1:/etc# getent passwd 'stephen'

Hi, this is my first post to this list, so please excuse if submitting a patch without previous discussion is considered bad form or anything similar. I encountered a bug in the CMake build while using MinGW (non-MSYS, non-CYGWIN) where the LTO_export fails with a "The syntax of the command is incorrect" error. This error was previously fixed for Windows in general using

I reacted as per my case. You need CFLAGS in order to what linker you might be using. In case of clang, you can use “-fuse-ld” to control the invocation of linker. In my opinion, it is not necessary to carry forward LDFLAGS unless you want to control specific parts of the linker. In my case, I have a cross compiler for ARM and I usually compile the code with Clang

[This email is either empty or too large to be displayed at this time]

Hello, I'm trying to compile llvm-gcc to crosscompile mips. I have already modified a config.gcc to add mips as a target with llvm, but it gives me "Did not get a target machine!" (from llvm-backend.cpp). I thought that I had to modify TargetMachOWriterInfo.h with MIPS info, but now the problem is that I don't know where can I get the <mach/machine.h> (I don't have it

Hi, On Wed, November 16, 2016 5:15 pm, Richard W.M. Jones wrote: > On Wed, Nov 16, 2016 at 05:09:56PM -0500, Derek Atkins wrote: > > I'll try to reproduce the issue here, but you can also do > the following command directly on the guest disk image if you > want to test something: > > time LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i > selinux-relabel

I have this project that I can't see how to boil down into a cut down illustration of the problem as it requires a large 3rd party library (ITK www.itk.org), and the problem is actually triggered in that library. But here is the problem: If you compile ITK and the program, it will segfault in _Unwind_resume at the end of a class method. If you build with GCC (4.6.1 in this case) the program