[CMake] Resource compiler issues for cross-compiling

Hi all, I'm cross-compiling from Linux to Windows using clang-cl and the Windows SDK (i.e. emulating an MSVC environment), and I'm attempting to use llvm-rc (which is new in LLVM 6.0) as the resource compiler. cmake automatically enables the RC language for MSVC. However, it also sets `CMAKE_NINJA

Re: [CMake] How to force use of Windows 64bit link.exe?

Running cmake from an x64 developer command prompt and passing -Thost=x64 to cmake should do the trick. On 11/8/17, 2:26 PM, "CMake on behalf of Paul Smith" wrote: Hi all. I wonder if someone can help me get CMake to force Visual Studio to run the 64bit linker instead of the 32bit link

Re: [CMake] Visual C++ Compile/Link Flags

Visual Studio's linker (and compiler, for that matter) also accept flags that start with dashes instead of slashes (e.g. you can do -opt:noref instead of /opt:noref). From: CMake on behalf of ThePhD Date: Tuesday, February 13, 2018 at 1:10 PM To: "cmake@cmake.org" Subject: Re: [CMake] Visual

Re: [CMake] Approach to both shared and static lib (again, sorry)

The convention in MSVC-land seems to be to prefix (as well as suffix) static libraries with lib. E.g. the static CRT is libcmt.lib, the static VC runtime support library is libvcruntime.lib (whereas the import library for the dynamic equivalent is vcruntime.lib), and so on. It isn't necessarily

[CMake] Framework installation problems with ninja

Am I doing something wrong, or is this a bug with CMake's Ninja generator? If it's the latter, any thoughts on how to work around it? I suppose I could try to manually create the "foo/foo.framework/foo" target, but that seems kinda gross. Thanks, Shoaib Meenai -- Powere

[CMake] Why does pkg_check_modules not use CMAKE_SYSTEM_PREFIX_PATH?

Hi, I'm using CMake for cross-compilation, and I have a toolchain file which sets CMAKE_SYSTEM_PREFIX_PATH accordingly. I'm running into issues with pkg_check_modules not finding some modules because it only searches inside CMAKE_PREFIX_PATH and not CMAKE_SYSTEM_PREFIX_PATH (where my *.pc files

Re: [CMake] Checking Variables in a tool-chain file

We have a somewhat similar problem with LLVM's toolchain file for cross-compiling to Windows, and we solve it there by saving and restoring cache variables from the environment inside the toolchain file itself. See https://reviews.llvm.org/diffusion/L/browse/llvm/trunk/cmake/platforms/WinMsvc.cm

Re: [CMake] Checking Variables in a tool-chain file

along to try_compile(). On Fri, Feb 1, 2019 at 6:36 AM Shoaib Meenai mailto:smee...@fb.com>> wrote: We have a somewhat similar problem with LLVM's toolchain file for cross-compiling to Windows, and we solve it there by saving and restoring cache variables from the envir

Re: [CMake] Fake dependencies of executables to static libs

elf-contained CMakeLists.txt that reproduces the issue, that'd also be helpful for debugging. Thanks, Shoaib Meenai From: CMake on behalf of Stephan Menzel Date: Wednesday, April 3, 2019 at 10:56 PM To: cmake Subject: Re: [CMake] Fake dependencies of executables to static libs Hello ag

Re: [CMake] cmake build of LLVM: HAVE_CXX_ATOMICS_WITHOUT_LIB test failure

llvm-...@lists.llvm.org would also be a good place to ask questions about the LLVM build system :) 1. I believe it’s just called the configure phase. (There’s also the generation phase, where CMake actually generates the build system.) 2. How have you set u

Re: [CMake] Need help with CMake error "CMake Error at tools/clang/lib/Headers/cmake_install.cmake:36 file INSTALL cannot find "C:/llvm-project/build/$(Configuration)/lib/clang/9.0.0/include"."

You're probably running into https://reviews.llvm.org/D58537#inline-532492. This is an LLVM issue, not a CMake issue. From: CMake on behalf of Osman Zakir Date: Monday, April 22, 2019 at 6:45 AM To: "cmake@cmake.org" Subject: [CMake] Need help with CMake error "CMake Error at tools/clang/lib

[CMake] Multiple exports for a target installation

Is it possible to associate a target with multiple exports? For example, if I'm building a project where I want to create multiple export sets, but there's some overlap in targets between those sets. I tried passing multiple EXPORT options to the install(TARGETS) signature but I just got an erro

Re: [CMake] Multiple exports for a target installation

COMPONENT option than the latest version, but I’ll cross that bridge when I get to it.) From: Craig Scott Date: Saturday, June 15, 2019 at 10:43 PM To: Shoaib Meenai Cc: "cmake@cmake.org" Subject: Re: [CMake] Multiple exports for a target installation On Sat, Jun 15, 2019 at 9:03 PM Sho

Re: [CMake] Multiple exports for a target installation

Thank you for the detailed explanation! That’s really helpful and gives me a much better sense of how to think about and structure this :) From: Craig Scott Date: Saturday, June 22, 2019 at 12:18 AM To: Shoaib Meenai Cc: "cmake@cmake.org" Subject: Re: [CMake] Multiple exports fo