[CMake] [VS] Error Code Return from add_custom_command() Suppresses Console Output

Hi, I have a custom command that calls an in-house compiler that generates a source file set up like this: add_custom_command(OUTPUT "generatedFile.h" COMMAND "myCompiler.exe -someParam" [..]) The compiler prints information to STDOUT like lines where errors or warnings occurred. When the

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

Cool. I try using this toolchain in a toy project, just to test, and execute the cmake inside cross-compiling x64_x86 from visual studio 2017 and all work as expected, except the linking from ninja, that break because cannot find printf. Is absolutely cool, better than my last toolchain. Do you

[Cmake-commits] CMake branch, master, updated. v3.15.3-1075-g1423507

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 1423507a71199fd76b457ad9b215a6caca70ee58 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-1072-g01cce69

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 01cce69870ec7efbb8138f5345aa7ffed8b7ac12 (commit) via

Re: [CMake] Difference between PRIVATE and PUBLIC with target_link_libraries

Hi, On Tue, Sep 17, 2019 at 04:21:36PM -0700, Alan W. Irwin wrote: > * It appears to me that if a CMake-based build system is configured > properly there is very little need for the PUBLIC option for TLL > because PRIVATE works well for shared libraries and the > PRIVATE-becomes-PUBLIC

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

We use ninja for building on Windows. Our toolchain file for the MSVC compiler is really simple (this is for MSVC 18.0, 32 bits): --- SNIP --- set(CMAKE_SYSTEM_NAME Windows) set(CMAKE_SYSTEM_PROCESSOR "x86") set(CMAKE_SYSTEM_VERSION 1) # Microsoft MSVC compiler set(CMAKE_C_COMPILER cl.exe)

[Cmake-commits] CMake branch, master, updated. v3.15.3-1068-g45b7d52

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 45b7d5284e11cb34885b756bee8dedeb94fc16cb (commit) from

Re: [CMake] Difference between PRIVATE and PUBLIC with target_link_libraries

Hi Craig: It appears you pretty much made the definitive statement about target_link_libraries (TLL) options at . However, I have some further questions about this key section of your statement: "[...] when A links in B as PRIVATE, the

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

Well, the Visual Studio Generator alone is not a option because the repository has a actual build system(a bunch of bat files that call a python script that generate ninja files). We want to change to cmake, and now we don't use Visual Studio a lot. Most of time, we only need their compiler and

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

As I recall for myself, simply using the Visual Studio Generator with the -A option was all that was needed to build for Win32. You don't need a toolchain file because the generator already knows how to setup a Visual Studio Project to target Win32. Even the documentation for cross-compiling

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

Thanks, I'll check it out. The toolchain file, as is, can generate ninja builds that can be used to generate a executable, but when I execute them, he say : ``` -- The C compiler identification is unknown -- The CXX compiler identification is unknown -- Check for working C compiler: C:/Program

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

>From my brief research, it looks like the Microsoft version of CMake may have Ninja support. https://devblogs.microsoft.com/cppblog/cmake-support-in-visual-studio-whats-new-in-2017-15-3-update/ Regards, Juan On Tue, Sep 17, 2019 at 1:36 PM Joao Pedro Abreu De Souza < jp_ab...@id.uff.br>

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

So, only the Visual Studio generator use the Arch option? I try generate ninja build, but cmake(3.15.3) and the answer was ``` $ cmake -B build -S . -G "Ninja" -A Win32 CMake Error at CMakeLists.txt:2 (project): Generator Ninja does not support platform specification, but platform

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

AFAIK you can set the generator in a CMakeSettings.json file if you are using MSVC. https://docs.microsoft.com/en-us/cpp/build/cmakesettings-reference?view=vs-2019 On 9/17/2019 10:00 AM, Juan Sanchez wrote: Hello, My impression that targeting 32 bit depends on what generator you are using.

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

Hello, My impression that targeting 32 bit depends on what generator you are using. https://cmake.org/cmake/help/git-stage/generator/Visual%20Studio%2015%202017.html It looks like cmake now has: - cmake -G "Visual Studio 15 2017" -A Win32 - cmake -G "Visual Studio 15 2017" -A x64 It used

Re: [CMake] system runtime library file does not exist (warning)

Hello, Somewhat related to your issue, is that newer versions of the Intel MKL are now free for use: https://software.intel.com/en-us/articles/free-ipsxe-tools-and-libraries Free Intel Performance Libraries for *Everyone* *Free for all,

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

On 9/17/19 2:17 PM Joao Pedro Abreu De Souza wrote: cl from visual studio 2017. Em ter, 17 de set de 2019 03:26, Stéphane Ancelot mailto:sance...@numalliance.com>> escreveu: Hi, That first depends on which compiler you will use ? Regards, S.Ancelot Le 16/09/2019 à

[Cmake-commits] CMake branch, master, updated. v3.15.3-1067-ge6ddb57

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e6ddb57479a3620c712719c120a7337a84470d21 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-1060-g42a20ef

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 42a20ef79b86090b65de9836158db2a59c837e69 (commit) via

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

cl from visual studio 2017. Em ter, 17 de set de 2019 03:26, Stéphane Ancelot escreveu: > Hi, > > That first depends on which compiler you will use ? > > Regards, > > S.Ancelot > Le 16/09/2019 à 22:32, Joao Pedro Abreu De Souza a écrit : > > Hi guys. I am trying to generate,using cmake, a

[CMake] system runtime library file does not exist (warning)

Hello, I have recent CMake 3.15.2 and old MKL library 11.1. Upon configuration cmake is issuing warnings due to faulty determined folder of general name FOLDER_lin (proper name is without lin): CMake Warning at

Re: [CMake] toolchain file - cross-compiling windows-amd64->windows-x86

Hi, That first depends on which compiler you will use ? Regards, S.Ancelot Le 16/09/2019 à 22:32, Joao Pedro Abreu De Souza a écrit : Hi guys. I am trying to generate,using cmake, a executable with target Windows 32 bits using Windows 64 bits, but cannot find a standard toolchain file (I

[Cmake-commits] CMake branch, master, updated. v3.15.3-1056-g3bc1fea

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 3bc1feae5fe044d796e4bcd932b7228c40fde230 (commit) from

[CMake] toolchain file - cross-compiling windows-amd64->windows-x86

Hi guys. I am trying to generate,using cmake, a executable with target Windows 32 bits using Windows 64 bits, but cannot find a standard toolchain file (I find to Linux, to Android, but can't find to Windows 32 bits) to build. Do you know some repository of toolchain files that has Windows 32 bits

Re: [CMake] Packaging a directory with CPack RPM

Le lun. 16 sept. 2019 à 18:12, Ashish Sadanandan < ashish.sadanan...@gmail.com> a écrit : > On Thu, Sep 12, 2019 at 4:57 AM Eric Noulard > wrote: > > > > > > > > Le jeu. 12 sept. 2019 à 02:27, Ashish Sadanandan < > ashish.sadanan...@gmail.com> a écrit : > > > > > Now may be you can tell CPack to

Re: [CMake] Packaging a directory with CPack RPM

On Thu, Sep 12, 2019 at 4:57 AM Eric Noulard wrote: > > > > Le jeu. 12 sept. 2019 à 02:27, Ashish Sadanandan > a écrit : >> >> Hello, >> I'm using CPack to create RPMs for an application. I have this working but >> the CPack step is quite slow. While investigating this, I noticed that all >>

[Cmake-commits] CMake branch, master, updated. v3.15.3-1055-g1ac4e0e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 1ac4e0ef1b29affc9e4f2cd86c4fc8c2252f2ab2 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-1053-g7c47894

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 7c47894b459c0f71ebe32b64a619f290df6bcf44 (commit) via

Re: [CMake] Preventing multiple definitions of metaObject methods

-Original Message- From: Kyle Edwards Sent: 13 September 2019 16:54 To: Stephen Morris ; cmake@cmake.org Subject: Re: [CMake] Preventing multiple definitions of metaObject methods >Stephen, >Could you post a minimally reproducible example with CMakeLists.txt and >accompanying source

Re: [CMake] Preventing multiple definitions of metaObject methods

-Original Message- From: Kyle Edwards Sent: 13 September 2019 16:54 To: Stephen Morris ; cmake@cmake.org Subject: Re: [CMake] Preventing multiple definitions of metaObject methods >Stephen, >Could you post a minimally reproducible example with CMakeLists.txt and >accompanying source

[Cmake-commits] CMake branch, master, updated. v3.15.3-1046-gbfa2eaa

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via bfa2eaa617de778ecfb2a0678c9898605822260d (commit) from

[Cmake-commits] CMake branch, master, updated. v3.15.3-1045-gc6ed044

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via c6ed04431988ac337ea21d74f035148b6c57f894 (commit) from

[CMake] find_path and double symbolic link

Hi all I have a weird situation where find_file finds a file (which is a link to a link), but find_path sets an empty variable. find_path(CBLAS_INCLUDE_DIR cblas.h PATHS /usr/include /usr/local/include ) message(STATUS "KT CBLAS_INCLUDE_DIR

[Cmake-commits] CMake branch, master, updated. v3.15.3-1044-g8032977

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 80329771fec7c516540e1db29d971f8f28ed593b (commit) from

Re: [cmake-developers] Proposal: Using smart pointers to own dynamically allocated memory

I will do that. It's also easier for me to track the changes that way. Regards, Tushar On Sat, Sep 14, 2019 at 12:04 AM Brad King wrote: > > On 9/13/19 1:30 PM, Tushar Maheshwari wrote: > > Thanks for the quick response. > > I have my commits separated by file groups. I'll open small MRs > >

Re: [cmake-developers] Proposal: Using smart pointers to own dynamically allocated memory

On 9/13/19 1:30 PM, Tushar Maheshwari wrote: > Thanks for the quick response. > I have my commits separated by file groups. I'll open small MRs > collecting the related groups. Thanks. Please just keep a couple MRs open at a time so we don't overwhelm the CI builders. After some are merged you

Re: [cmake-developers] Proposal: Using smart pointers to own dynamically allocated memory

Thanks for the quick response. I have my commits separated by file groups. I'll open small MRs collecting the related groups. Please comment if the grouping is incorrect or if a commit/diff needs to be moved to a different branch. Thanks, Tushar On Fri, Sep 13, 2019 at 10:46 PM Brad King wrote:

Re: [cmake-developers] Proposal: Using smart pointers to own dynamically allocated memory

On 9/13/19 12:58 PM, Kyle Edwards via cmake-developers wrote: > On Fri, 2019-09-13 at 22:08 +0530, Tushar Maheshwari wrote: >> I have pushed some sample commits to >> https://gitlab.kitware.com/tusharpm/cmake/commits/smart_mem. >> >> If this is something I can pursue, I would appreciate a review

Re: [cmake-developers] Proposal: Using smart pointers to own dynamically allocated memory

On Fri, 2019-09-13 at 22:08 +0530, Tushar Maheshwari wrote: > Hi, > > I am a C++ developer and a modern-C++ enthusiast. In the interest of > modernizing the codebase, I propose using smart pointers to handle > dynamically allocated memory. I would like to get the feedback from > the developers if

[cmake-developers] Proposal: Using smart pointers to own dynamically allocated memory

Hi, I am a C++ developer and a modern-C++ enthusiast. In the interest of modernizing the codebase, I propose using smart pointers to handle dynamically allocated memory. I would like to get the feedback from the developers if this change is planned/attempted/desirable or inapplicable for CMake.

Re: [CMake] Preventing multiple definitions of metaObject methods

On Fri, 2019-09-13 at 15:25 +, Stephen Morris wrote: > Suppose I have a class that derives from QObject, and contains the > Q_OBJECT macro in its header file. When I compile it using AUTOMOC > enabled, a "moc_myClass.cpp" file is created; if I manually include > that file at the end of my

[CMake] Preventing multiple definitions of metaObject methods

Suppose I have a class that derives from QObject, and contains the Q_OBJECT macro in its header file. When I compile it using AUTOMOC enabled, a "moc_myClass.cpp" file is created; if I manually include that file at the end of my 'myClass.cpp" file, then the moc file will be compiled there,

[Cmake-commits] CMake branch, master, updated. v3.15.3-1043-g19bcdca

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 19bcdca93c3a05db12652677f8d0e310797bb375 (commit) via

Re: [CMake] set_target_properties ( INTERFACE_INCLUDE_DIRECTORIES ...)

For completeness, there is also OPTION C: set_property(TARGET target PROPERTY INTERFACE_INCLUDE_DIRECTORIES directory1 directory2) set_target_properties() is a shorthand for setting several properties at once, so it assumes its arguments are prop value prop value. If you need finer control,

Re: [CMake] set_target_properties ( INTERFACE_INCLUDE_DIRECTORIES ...)

On Thu, Sep 12, 2019 at 6:31 PM Craig Scott wrote: OPTION A: Put quotes around a semi-colon separated string if using > set_target_properties(): > Many thanks. I had tried quotes, and I had tried a semi-colon, and I thought that I had tried them together, but evidently I missed that

[Cmake-commits] CMake branch, master, updated. v3.15.3-1015-g729c928

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 729c928c7b59919a9d379891973bda22665c75da (commit) from

Re: [CMake] set_target_properties ( INTERFACE_INCLUDE_DIRECTORIES ...)

On Fri, Sep 13, 2019 at 8:24 AM Theodore Hall wrote: > Greetings, > > set_target_properties(target PROPERTIES > IMPORTED_LOCATION location > IMPORTED_IMPLIB implib > INTERFACE_INCLUDE_DIRECTORIES directory+ > ) > > Is there a way to assign more than one directory to >

[CMake] set_target_properties ( INTERFACE_INCLUDE_DIRECTORIES ...)

Greetings, set_target_properties(target PROPERTIES IMPORTED_LOCATION location IMPORTED_IMPLIB implib INTERFACE_INCLUDE_DIRECTORIES directory+ ) Is there a way to assign more than one directory to INTERFACE_INCLUDE_DIRECTORIES ? The property name is plural, but every attempt I've

[CMake] compile_commands.json question

Hi all, this is more a question to the cmake developers. Older versions (3.15.0) of cmake produced short file names w/o spaces on windows, when the path of the compiler executable contained spaces. Now I have an issue [1] where compiler executable path contains spaces with cmake 3.15.2. Can

Re: [CMake] Setting RPATH lookup on macOS

I never suggested copying files into the build tree. The original question was about how to locate libraries at runtime. You don't necessarily have to use @rpath, @executable_path is also a valid option. Another valid option one is to strip out @rpath and use DYLD_LIBRARY_PATH or

Re: [CMake] Setting RPATH lookup on macOS

On macOS you really should _not_ have to copy the libraries into the build tree. I have never had to do that in 10 years of our product (Windows is a different story). The trick is setting the correct options to add in the paths to the libraries into the RPATH of the executable/library. (at

Re: [CMake] Setting RPATH lookup on macOS

The macOS install_name_tool can be used to change the RPATH of your binaries. It can also be used to set the path for each of the libraries to be loaded. For a python module I compile, I copy each of its dylib into the appropriate directory relative to my shared library. I then use the

[Cmake-commits] CMake branch, master, updated. v3.15.3-1014-g9602bcf

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 9602bcfc62d50d7bb302b02ae3b1f9afe941bae7 (commit) via

Re: [CMake] Packaging a directory with CPack RPM

Le jeu. 12 sept. 2019 à 02:27, Ashish Sadanandan < ashish.sadanan...@gmail.com> a écrit : > Hello, > I'm using CPack to create RPMs for an application. I have this working but > the CPack step is quite slow. While investigating this, I noticed that all > files in a directory I'm packaging, which

[CMake] can not import target external lib before being build

Hi, I am using this cmake snippet in order to build an external library # -- QGLViewer -- set(QGLVIEWER_FILES ${CMAKE_BINARY_DIR}/libQGLViewer-2.7.1/QGLViewer/qglviewer.h) get_target_property (QT_QMAKE_EXECUTABLE Qt5::qmake IMPORTED_LOCATION) add_custom_command(OUTPUT

[Cmake-commits] CMake branch, master, updated. v3.15.3-1008-g5bdff30

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 5bdff304847995f474797b757fe7a2755de0c1fb (commit) from

[CMake] Packaging a directory with CPack RPM

Hello, I'm using CPack to create RPMs for an application. I have this working but the CPack step is quite slow. While investigating this, I noticed that all files in a directory I'm packaging, which contains a large number of small files, is being listed in the spec file. For instance, say I have

Re: [CMake] Setting RPATH lookup on macOS

On 9/11/19, 5:42 PM, "Kyle Edwards" wrote: On Wed, 2019-09-11 at 17:33 -0400, Michael Jackson wrote: > Already looked on google and at the CMake documentation but > everything listed does not seem to work so here is the setup. > > I am using MKL and I have a home grown

Re: [CMake] Setting RPATH lookup on macOS

On Wed, 2019-09-11 at 17:33 -0400, Michael Jackson wrote: > Already looked on google and at the CMake documentation but > everything listed does not seem to work so here is the setup. > > I am using MKL and I have a home grown FindMKL since there isn’t an > official one. Inside that is the

[CMake] Setting RPATH lookup on macOS

Already looked on google and at the CMake documentation but everything listed does not seem to work so here is the setup. I am using MKL and I have a home grown FindMKL since there isn’t an official one. Inside that is the typical find_library() calls which will find the libraries just fine.

Re: [CMake] Should header files be listed for a target?

On Mittwoch, 11. September 2019 21:22:04 CEST Kyle Edwards via CMake wrote: > On Wed, 2019-09-11 at 22:00 +0300, Avraham Shukron wrote: > > On Wed, Sep 11, 2019 at 9:49 PM Kyle Edwards > > > m> wrote: > > > You can list them or not list them. CMake will recognize them as > > > header > > > files

Re: [CMake] Should header files be listed for a target?

On Wed, 2019-09-11 at 22:00 +0300, Avraham Shukron wrote: > > > On Wed, Sep 11, 2019 at 9:49 PM Kyle Edwards m> wrote: > > You can list them or not list them. CMake will recognize them as > > header > > files and ignore them (not attempt to compile them.) It's a matter > > of > > personal

Re: [CMake] Should header files be listed for a target?

On Wed, Sep 11, 2019 at 9:49 PM Kyle Edwards wrote: > You can list them or not list them. CMake will recognize them as header > files and ignore them (not attempt to compile them.) It's a matter of > personal preference. CMake's own CMake script lists them, but there are > plenty of projects

Re: [CMake] Should header files be listed for a target?

On Wed, 2019-09-11 at 21:40 +0300, Avraham Shukron wrote: > Hi! > > I'm pretty new to cmake and I came across a question which I could > not find any information about in the official documentation or blog > posts. > > When adding a target through add_library / add_executable - should > the

[CMake] Should header files be listed for a target?

Hi! I'm pretty new to cmake and I came across a question which I could not find any information about in the official documentation or blog posts. When adding a target through add_library / add_executable - should the header files of the target also be listed? The question also applies to

[Cmake-commits] CMake branch, master, updated. v3.15.3-1007-gb5b10c8

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via b5b10c8e955abb2b0f18c3e41b7892471857bcc1 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-994-g7f46e4a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 7f46e4a73a4d7aaa4029a04c532d2c99635383b9 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.15.3-993-g95d4a2d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 95d4a2d05562c5f0a4113527d31dadef4d7756bd (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-988-gbbf48c4

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via bbf48c494ad28d1c8ac5aa6e4cecb35c2cbf1b84 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-986-g05d5c66

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 05d5c66ff853f88e6dbe43bbddd18dd8babaa427 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-977-gc2ead49

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via c2ead49451cdd29da50954c88d45334694026ad0 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-975-gf9a014e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via f9a014e2c810799e0c148e44a2237704fdba717d (commit) from

Re: [CMake] try_compile with multiple include directories

Yes, semicolon worked. Thanks Kyle and Jakub for the responses. Isuru On Mon, Sep 9, 2019 at 9:04 AM Kyle Edwards wrote: > On Sun, 2019-09-08 at 14:07 -0500, Isuru Fernando wrote: > > Hello, > > > > I can use the following to get try_compile to include one directory. > > > > CMAKE_FLAGS

Re: [CMake] try_compile with multiple include directories

On Sun, 2019-09-08 at 14:07 -0500, Isuru Fernando wrote: > Hello, > > I can use the following to get try_compile to include one directory. > > CMAKE_FLAGS "-DINCLUDE_DIRECTORIES=dir1" > > How do you use try_compile when I have multiple directories to pass > to it? > > Isuru Use a semicolon:

[Cmake-commits] CMake branch, master, updated. v3.15.3-974-g922482d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 922482dd3acd2af9d26476134b3386c5a7695a03 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-972-gd803d6b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via d803d6b59f294b1bd1bd32beb75468399560be95 (commit) from

[CMake] try_compile with multiple include directories

Hello, I can use the following to get try_compile to include one directory. CMAKE_FLAGS "-DINCLUDE_DIRECTORIES=dir1" How do you use try_compile when I have multiple directories to pass to it? Isuru -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

[CMake] Specify "NO multilib" for cross compilation ???

Hi, all: I'm trying to cross compile a package with CMake. I strictly followed the documentation here: https://cmake.org/cmake/help/latest/manual/cmake-toolchains.7.html But, still obtained the following ERROR messages: CMake Error at

[Cmake-commits] CMake branch, master, updated. v3.15.3-971-gc52a354

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via c52a354244086a3ad591ae01eb506ec5851bcfc2 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.15.3-970-g9aecf2e

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 9aecf2e84016568d41cd199eb8a57d370f442041 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.15.3-969-gca8c3d6

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via ca8c3d64c8accebeacf322f0574494ffddb039c5 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-962-g7772c1d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 7772c1db03b2424d0b8bc0f7b89e5733d2770b1d (commit) from

[Cmake-commits] CMake branch, master, updated. v3.15.3-961-ga2d4968

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via a2d4968ab914d5cf02457306ec8f76177a794520 (commit) via

[CMake] fortran end of file error in object files

Dear all, I am working on some fortran code that links to c++, and have run into an issue where make doesn't like the generated object file. There is something weird going on either in the preprocessing or something weird with my machine. What is weird is that people with the same OS,

[Cmake-commits] CMake branch, master, updated. v3.15.3-959-g6db8f6a

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 6db8f6a410d99e9a66847530bb520b329d2f1a9e (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-957-gac4d6d4

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via ac4d6d4a9d9b81773e61c643169cb2afe1bab644 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-952-gfcba9c3

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via fcba9c3baa00631407f493f97afe7e9cd1b844a7 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.3-949-gf545428

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via f545428be08531d2561feba4854793775be83c39 (commit) from

Re: [CMake] The connection to cmake-server was terminated unexpectedly [cms-client] cmake-server exited with status null (SIGSEGV)

Awesome thank you so much! So i’ve upgraded to 3.15.3 and it’s told me perfectly my issue. So I have an override script (FindLibXml2.cmake): *** START CODE *** # FindLibXml2.cmake # # A wrapper around CMake's FindLibXml2 which provides an imported

Re: [CMake] The connection to cmake-server was terminated unexpectedly [cms-client] cmake-server exited with status null (SIGSEGV)

On Thu, Sep 5, 2019 at 7:56 AM Christopher Dawes < christopher.da...@eftlab.com> wrote: > Awesome thank you so much! So i’ve upgraded to 3.15.3 and it’s told me > perfectly my issue. So I have an override script (FindLibXml2.cmake): > > *** START CODE

Re: [CMake] The connection to cmake-server was terminated unexpectedly [cms-client] cmake-server exited with status null (SIGSEGV)

On Wed, 2019-09-04 at 14:12 -0400, fdk17 wrote: > https://github.com/microsoft/vscode-cmake-tools/issues/752 states > that it ran out of stack and the log shows what looks like to be > involved with a recursive loop in some CMakeLists.txt.  A call depth > of 27491 seems a bit excessive. > > After

Re: [CMake] The connection to cmake-server was terminated unexpectedly [cms-client] cmake-server exited with status null (SIGSEGV)

https://github.com/microsoft/vscode-cmake-tools/issues/752 states that it ran out of stack and the log shows what looks like to be involved with a recursive loop in some CMakeLists.txt. A call depth of 27491 seems a bit excessive. After the second call to FindPackage it just seems to be doing

[CMake] The connection to cmake-server was terminated unexpectedly [cms-client] cmake-server exited with status null (SIGSEGV)

Hi there, we are experiencing a crash when working with VSCode on Ubuntu: Brief Issue Summary When starting up VSCode using the CMake extension i get this error on all my projects, the application terminates pretty quickly. What’s happening is cmake server is spawned and then crashes; i’m

[cmake-developers] [ANNOUNCE] CMake 3.15.3 available for download

We are pleased to announce that CMake 3.15.3 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.15.3 since 3.15.2:

[CMake] [ANNOUNCE] CMake 3.15.3 available for download

We are pleased to announce that CMake 3.15.3 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.15.3 since 3.15.2:

[Cmake-commits] CMake annotated tag, v3.15.3, created. v3.15.3

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The annotated tag, v3.15.3 has been created at 842f4e2244ec87b814624c97be6456b3d68d3f6c (tag) tagging

[Cmake-commits] CMake branch, release, updated. v3.15.2-34-g26a0e20

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 26a0e200e5f4abe8268235c9fdb23a2612a1b3b1 (commit) from

[Cmake-commits] CMake branch, master, updated. v3.15.2-982-gee15bc7

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via ee15bc7d7e7707fd8d7db92645c2c56a5df0f681 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.15.2-980-gaef152b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via aef152b91d9f56af87ca2b9618f07228e5f3c463 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.15.2-33-g7a8bd12

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 7a8bd12926c32f709cc162ba931484c1b5820363 (commit) via

<    3   4   5   6   7   8   9   10   11   12   >