Re: [CMake] Unknown generator output with CMake

2017-03-28 Thread Craig Scott
I have a very similar situation at work to yours. We build a generator which produces source files, but we don't know the set of source files that will be produced until after the generator has been run. The solution that is working for us is documented here: http://stackoverflow.com/a/36084786/19

[CMake] Unknown generator output with CMake

2017-03-28 Thread Jeandet Alexis
Hi, I play with CMake on PythonQt build. I faced a chalenge: PythonQt is composed of: 1)The generator which wrap Qt api(parses Qt sources to produce cpp/python wrappers) 2)The Lib (main engine) 3)The wrappers generated by 1) The chalenge was to build in this order:

Re: [CMake] Visual Studio 2017 could not be found if installed in non-default location

2017-03-28 Thread Nils Gladitz
On 03/28/2017 03:57 PM, HarpyWar wrote: "Microsoft.VisualStudio.Component.Windows81SDK" could not not be found anywhere. A component "Microsoft.VisualStudio.Component.Windows10SDK.14393" exists on Windows 10 x64 (just found about it here https://docs.microsoft.com/en-us/visualstudio/install/

Re: [CMake] Visual Studio 2017 could not be found if installed in non-default location

2017-03-28 Thread HarpyWar
"Microsoft.VisualStudio.Component.Windows81SDK" could not not be found anywhere. A component "Microsoft.VisualStudio.Component.Windows10SDK.14393" exists on Windows 10 x64 (just found about it here https://docs.microsoft.com/en- us/visualstudio/install/workload-component-id-vs-community) This co

Re: [CMake] Visual Studio 2017 could not be found if installed in non-default location

2017-03-28 Thread Nils Gladitz
On 03/28/2017 03:17 PM, HarpyWar wrote: Nils Gladitz, the command, which you proposed, return nothing, even on a machine where a compiler found: vswhere -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -requires Microsoft.VisualStudio.Component.Windows10SDK For me it lists my "Visu

Re: [CMake] Visual Studio 2017 could not be found if installed in non-default location

2017-03-28 Thread HarpyWar
I did some tests on different Windows versions in virtual machines. On a fresh Windows 10 (and installed Visual Studio 2017 Community) cmake works fine and a compiler is found. But on earlier versions: Windows 7, Windows 8.1, Windows Server 2012 - cmake always fails with error "The CXX compiler id

Re: [CMake] Toggle Absolute paths in Eclipse Generator

2017-03-28 Thread Eric Noulard
Hi Michele, If you look into CMake ML history you'll find many discussions concerning the ABSOLUTE vs RELATIVE path for generated build systems. CMake had once an option for trying that, the support has been removed: https://cmake.org/cmake/help/v3.7/variable/CMAKE_USE_RELATIVE_PATHS.html So bas

[CMake] Add BUILD_SHARED_LIBS as an option

2017-03-28 Thread Mateusz Loskot
Hi, The docs [1] say: "This variable [BUILD_SHARED_LIBS] is often added to projects as an option()" [1] https://cmake.org/cmake/help/latest/variable/BUILD_SHARED_LIBS.html Does that literally mean adding the option this way? option(BUILD_SHARED_LIBS "Build shared library" OFF) Or, adding an e

[CMake] Toggle Absolute paths in Eclipse Generator

2017-03-28 Thread Michele Portolan
Hello, I am trying to use the Eclipse Generator to create a project to be exported to Eclipse. Everything works fine, but when I look at the generated .cproject and .project I see that all paths are absolute, like for instance: -E chdir "/home/portolan/my_project/Optional_Libs/eclipse_build