Re: [CMake] Crosscompilation woes

I am using a toolchain file! The CC and CXX environment variables are set by CMake (I assume, because I haven’t touched them). I’ll disect the link to see what I’ve missed. Regards /R From: Craig Scott [mailto:craig.sc...@crascit.com] Sent: den 10 oktober 2016 13:56 To: Robert Bielik

Re: [CMake] Error with ninja generator when using target_link_library with the debug keyword

Hi, I just want to confirm that I have the same problem on Windows with the Ninja generator. Even when I always use both keywords (debug & optimized) in my *target_link_libraries *commands I still got a *ninja.build *file that has bad $-escape characters. I think that this problem is happening

Re: [CMake] Crosscompilation woes

It is pretty much standard. I wrote the toolchain file adapting different examples. the Cmakelist is for the subdirectory of my parser (called SIT_parser). The trick si that I use a custom command for Lex/Yacc, so even when cross-compiling it is still correctly called. Michele Le

Re: [CMake] Crosscompilation woes

Aha, I see. You're using find_package. That will automatically get you the binaries for your host system. My problem is different, I need to build my binaries with CMake before using them, and I need to build them with i686 (instead of arm). Regards /R From: portolan

Re: [CMake] Crosscompilation woes

I’m trying to do this, but since I setup a cross compiling env. by setting C++ compiler, these settings get used when I run execute_process to setup the host build !! Thus I get the ARM version of the build tools anyway! :( It seems that when execute_process is executed, the CC and CXX

Re: [CMake] Crosscompilation woes

Don't use environment variables to set the ARM compilers in your situation, use a toolchain file to specify them instead. Your CMake experience will generally be smoother if you specify cross-compile details via toolchain files. If you are following the method in the stackoverflow link I mentioned

Re: [CMake] CMake doesn't detect Microsoft Build Tools 2015 on Windows 10

Please open a bug, I can take a look at it. From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Eduard Wirch Sent: Monday, October 10, 2016 02:41 To: cmake@cmake.org Subject: [CMake] CMake doesn't detect Microsoft Build Tools 2015 on Windows 10 Hi I've installed build tools from here:

[CMake] Crosscompilation woes

Hi all, I am crosscompiling a project for arm (on linux i686), and use codegeneration tools within the project (together with add_custom_command). Of course, this will fail, since the tools are compiled for arm also and thus won't execute on my host system. So the tools need to be compiled for

Re: [CMake] Crosscompilation woes

Here's one possible solution (not perfect, but has been working in production for us for a while now for a similar scenario to what you describe): http://stackoverflow.com/q/36084785/1938798 An alternative is a superbuild arrangement which would require a top level project to drive two

Re: [CMake] Crosscompilation woes

Thanks Craig, Your solution will work for me I think. Regards /R From: Craig Scott [mailto:craig.sc...@crascit.com] Sent: den 10 oktober 2016 10:47 To: Robert Bielik Cc: Cmake@cmake.org Subject: Re: [CMake] Crosscompilation woes Here's one possible solution (not

Re: [CMake] Crosscompilation woes

In my project I build on Linux i686 and I use a Toolchain file to specify the ARM cross-compiler https://cmake.org/cmake/help/v3.6/manual/cmake-toolchains.7.html The nice thing is that if you mark some files as "generated" CMAKE will automatically use the build rather than the target

Re: [CMake] Crosscompilation woes

I cannot answer your question: I am a newcomer to Cmake (I have been using it for less than 6 months) and on my build system I have 3.6, so I never really looked at the previous versions. Sorry, Michele Le 10/10/2016 à 11:30, Robert Bielik a écrit : Thank you Michele, This is exactly

Re: [CMake] Crosscompilation woes

Ok, I cannot get this to work. The source files to be generated with add_custom_command have property GENERATED set to ON, but cmake does not adhere, and tries to use the tool binaries of the target system. Michele, would you be ok with sharing your cmake code for this particular bit ? Regards

Re: [CMake] Crosscompilation woes

Thank you Michele, This is exactly what I'm after. You specify cmake v3.6 docs ? Is it only working from 3.6.x ? I have 3.5.2 on my build system. Regards /Robert From: portolan [mailto:michele.porto...@imag.fr] Sent: den 10 oktober 2016 11:27 To: Robert Bielik ; Craig

[CMake] CMake doesn't detect Microsoft Build Tools 2015 on Windows 10

Hi I've installed build tools from here: http://landinghub.visualstudio.com/visual-cpp-build-tools But CMake will automatically detect (and choose) Visual Studio 8 (installed here as well) instead. Looking into the source: const std::string vsregBase =

[CMake] [SOLVED] RE: Crosscompilation woes

For reference: I went with Brads suggestion: https://gitlab.kitware.com/cmake/cmake/issues/16356 which seems to be working fine. Regards /R From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Robert Bielik Sent: den 10 oktober 2016 14:00 To: Craig Scott Cc:

Re: [cmake-developers] Patch: Don't emit warning when config file not found

On 10/09/2016 03:24 PM, Christoph Grüninger wrote: > * or loosing the output of tests and feature summary, as both tests are QUIET. > > I'd prefer to write the error message to the CMakeError.log and reduce > the output to one line. I think, the current behavior must be considered > a bug. The

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-313-g479b0e2

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, next has been updated via 479b0e2175da23aa995c19cc03d2abbfae1ea551 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-90-gd3f1fcf

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-86-gce00292

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-100-g9c7fc00

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 9c7fc00a45b6f0891c95fba707b0e2ce9d2e2dbf (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-93-ge8cdbec

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-95-g211e322

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 211e3223a6f96800b5c7187a58715a8e1e081869 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-88-g19d4f94

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 19d4f942fe5fe2d84e9fc1f6abe9c237f6dceeec (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-110-g8fe948c

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 8fe948c54cd0a7a06b5c56e8a40dab945c5a08e7 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-137-g1e6aaef

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 1e6aaefdeebbf09eaf7fa0e9dbc6a7faa2f9132a (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-325-gd3f418e

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, next has been updated via d3f418e5be2c94933abfccf13e3aea031472c949 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-362-g275217f

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, next has been updated via 275217f7c9a7b0252643b50f0431001802499daa (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-164-g656ebac

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 656ebaca3be50e92edca3d9628b784f5ff1e6a99 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-342-gdd75faf

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, next has been updated via dd75faf01aecc93c32cbc5941d29033e33af0521 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-360-gf62d2c8

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, next has been updated via f62d2c869f7ebbb418bde71bff2ecbfc7a3993b2 (commit) via

Re: [cmake-developers] FastBuild Generator

On 10/10/2016 09:39 AM, Charles Huet wrote: > * the test CMake.CheckSourceTree does not work with Fastbuild, > but I could not get it to work with Ninja either, maybe I > have an environment problem ? It works with Ninja for me. Are you building CMake out-of-source? > * the test

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-366-ge5c68d0

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, next has been updated via e5c68d04f4eb28ab4f967fe1f127be6b28c0ec92 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-382-g885c6f5

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, next has been updated via 885c6f5f348a45174cf5e3a799dc8c0f13c37e67 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-364-g6cb01ac

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, next has been updated via 6cb01ac244b6476c2677cf2b2114e9044886c747 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-384-g17bef2c

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, next has been updated via 17bef2cd6780731f77be1383f74ddb5d9c44bffc (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-394-g67c528c

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, next has been updated via 67c528c03d2c598e4922f932c5598d5da91bc408 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-165-g2fb8e5b

_VERSION_MINOR 7) -set(CMake_VERSION_PATCH 20161010) +set(CMake_VERSION_PATCH 20161011) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [cmake-developers] FastBuild Generator

Hi again. I performed all the aforementioned actions, please check everything is OK for you. I have a few questions: * the test CMake.CheckSourceTree does not work with Fastbuild, but I could not get it to work with Ninja either, maybe I have an environment problem ? * the test SimpleInstall

[Cmake-commits] CMake branch, release, updated. v3.7.0-rc1-32-g9f240cf

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 9f240cff8ad14832dbc5472917b3b2e3fe813e46 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-340-g1b79da2

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, next has been updated via 1b79da2c9939c0674970d36ca282f0e4f62fa8c5 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-146-g06b71ff

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 06b71ff9fb41369e6dce0c2b9760d2d546d47dec (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-330-g92810dc

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, next has been updated via 92810dc819dc45bad1a7aff6bb10b82c9d2451f7 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-327-g3826f1c

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, next has been updated via 3826f1c832b071df8bb7163d44ad1981724ad70b (commit) via