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:
htt
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: Cmake@cmake.org
Subject: Re: [
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 on
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
Cc: Cmake
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
I’m trying to do this, but since I setup a cross compiling env. by setting
C&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 environ
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 [mailto:michele.porto...@i
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 10/10/2
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
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 =
"[HKEY_LOCAL_MACHINE\\SOFTWARE\
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 toolchain
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 wha
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 Scott
Cc: Cmake@cmake.or
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 perfect, but has been working i
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 sub-builds
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
16 matches
Mail list logo