[cmake-developers] Antwort: Re: Non supported toolchain

Hi Alex, thanks for your answer. 1. is there some guide or at least some example? 2. Does this module needs to be in the offical build to be distributed or is there a possibility to distribute the modules locally? Thanks! Oli Von:Alexander Neundorf An:

[Cmake-commits] CMake branch, master, updated. v3.10.0-399-ge1243a5

VERSION_MINOR 10) -set(CMake_VERSION_PATCH 20171122) +set(CMake_VERSION_PATCH 20171123) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Antwort: Re: Re: Antwort: Antwort: Re:Antwort: Re: Toolchain with non-gcc argument format

Hi! One solution is to write a wrapper script in your favourite scripting language (Ruby, Python etc) that pretend that it's a compiler. It could recognise the -I option and start the RX compiler with the --include option. It would not hurt to make it recognise other standard flags like "-o" and

Re: [cmake-developers] Non supported toolchain

On 2017 M11 22, Wed 10:37:00 CET oliver.za...@egoproducts.com wrote: > Hi, > > i know this is the dev mailing list, but i tried to solve my problem in > the normal one (see here > https://www.mail-archive.com/cmake@cmake.org/msg57862.html) with no > success. > > In Short: i have a toolchain for

[cmake-developers] Compiler changes on voyager.sf-tec.de

I will remove gcc 4.8 on voyager now. There will be a gcc 6.4 eventually as replacement. Greetings, Eike signature.asc Description: This is a digitally signed message part. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] Cannot seem to add include directory

Well, that's the standard way to add include for msbuild projects, other variables are meant to be used for the tool chain includes only Le mer. 22 nov. 2017 à 20:04, Michael Powell a écrit : > On Wed, Nov 22, 2017 at 1:45 PM, Michael Powell >

Re: [CMake] Cannot seem to add include directory

On Wed, Nov 22, 2017 at 1:45 PM, Michael Powell wrote: > Hello, > > I have a couple of libraries added, one SHARED and the other STATIC, > for which I want to add include directories, but they are not adding. Oh, okay... So they are being added under "additional include

[CMake] Cannot seem to add include directory

Hello, I have a couple of libraries added, one SHARED and the other STATIC, for which I want to add include directories, but they are not adding. I am trying the following: target_include_directories (${MY_PROJECT_NAME_SHARED} PUBLIC "G:/Source/Boost.Installed/boost-1.65.1/include" ) Where

Re: [CMake] spaces in generator strings troublesome (Michael Ellery)

Hi Michael Ellery thank you for your reply. > perhaps handle arguments as an array variable in bash - it?s a > slightly saner way to deal with args with spaces: > > CMDLINE=(. -G"Unix Makefiles") && cmake "${CMDLINE[@]}? Well i already got it working in bash when i wrote that. I have the

[CMake] Toolchain files and vcpkg

Hi! I’m trying to use packages (HPX specifically) installed with vcpkg, and according to its wiki, it is easiest to do so via the toolchain file provided by vcpkg. Here’s is what I’m doing: cd build cmake -G „Ninja” -D CMAKE_BUILD_TYPE=Release -D

Re: [CMake] Handling of generator expressions

Dear Oleksii, indeed it works! Thank you! I have opened an issue on the CMake repository: https://gitlab.kitware.com/cmake/cmake/issues/17501 I think it could still be a bug, since target_compile_definitions and target_link_libraries seem to evaluate the expression differently. All the best,

[Cmake-commits] CMake branch, master, updated. v3.10.0-398-g51ccfaa

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 51ccfaacb88303bb2774cead91069e1c25888137 (commit) via

Re: [cmake-developers] custom_command and compile_commands.json

Well, my impression was that it is generally for external tools to be aware of the build process, or the commands CMake executes. compile_commands.json is how Microsofts C++ extension to Visual Studio Code fetches compiler definitions and include directories. See last paragraph of:

Re: [CMake] Using find_package() portably?

On Mittwoch, 22. November 2017 11:32:22 CET Carsten Fuchs wrote: > That is, follow-up question: near the "..." above, we have got a target > "libjpeg", but how do I get the variables JPEG_INCLUDES, JPEG_LIBRARIES > etc. that `find_package(JPEG)` normally provides so that the last line > with the

Re: [CMake] Using find_package() portably?

22.11.2017, 13:37, "Carsten Fuchs" : > Hi all, > > thanks to you all for your replies! > > Concluding from your replies, it seems that the following approach for > each external dependency implements a good(?) solution: > > find_package(JPEG) # without "REQUIRED" > > if

Re: [CMake] Handling of generator expressions

UPD. forgot to CC the mailing list Hi, I am also confused by this and decided to test it. I found a long thread from 2012 that discusses list expansion issues. It doesn't tell though whether the patch was mainlined.

Re: [CMake] Using find_package() portably?

Hi all, thanks to you all for your replies! Concluding from your replies, it seems that the following approach for each external dependency implements a good(?) solution: find_package(JPEG) # without "REQUIRED" if (NOT JPEG_FOUND) # Optionally, under Linux only: # Stop with

[cmake-developers] Non supported toolchain

Hi, i know this is the dev mailing list, but i tried to solve my problem in the normal one (see here https://www.mail-archive.com/cmake@cmake.org/msg57862.html) with no success. In Short: i have a toolchain for an microcontroller (renesas rx serjes) running on windows. I want to build my

[CMake] Antwort: Re: Re: Antwort: Antwort: Re:Antwort: Re: Toolchain with non-gcc argument format

Hi Eric, thanks a lot for your help! i'm going to try it on the dev mailing list. Cheers, Oliver Von:Eric Noulard An: oliver.za...@egoproducts.com Kopie: CMake Mailinglist Datum: 22.11.2017 09:49 Betreff:Re: Re: [CMake] Antwort:

Re: [CMake] Strange error with brand new CMake 4.10.0 - SOLVED

What a shame! Actually that error message comes from my own CMakeLists.txt file - where I had so far only configured some settings for Linux and not yet for MSVC... This is indeed not any more the MT problem, but simply my own - so please forget about my previous posting! Regards, Cornelis Am

[CMake] Strange error with brand new CMake 4.10.0

Yesterday I had a problem with the CMake release candidate 4 for the version 4.10.0 on Windows with MSVC 2015, and I realized by reading the CMakeOutput.log that testing the Manifest Tool (MT) was failing. And with a little Google I got the impression that this is now fixed with the final release:

Re: [CMake] Antwort: Antwort: Re:Antwort: Re: Toolchain with non-gcc argument format

Hi Olivier, Putting the list back. You may try developer list as well. 2017-11-22 9:02 GMT+01:00 : > Hi, > > Is there really no way to override this var with a toolchain file? that > seems somehow strange to me, since CMAKE is so configurable that i can't > change