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

2019-09-18 Thread Eric Doenges
If the environment is set up correctly, the MSVC tools should be able to find the correct versions of the runtime libraries automatically. If you are using the wrapper script approach, the problem is most likely that when using MSVC, linking is done by calling the linker directly instead of ind

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

2019-09-18 Thread Marek Vojtko
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 co

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

2019-09-18 Thread Joao Pedro Abreu De Souza
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 kno

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

2019-09-18 Thread Simon Richter
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 beha