[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

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

[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

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

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

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

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

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:

[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-developers] Support for version suffixes

2017-03-28 Thread Daniel Pfeifer
On Mon, Mar 27, 2017 at 11:03 PM, Roger Leigh wrote: > Hi folks, > > I'd like to bring this issue to your attention to canvas some feedback > regarding the use of version suffixes: > > https://gitlab.kitware.com/cmake/cmake/issues/16716 > > This is basically a proposal to

Re: [cmake-developers] Support for version suffixes

2017-03-28 Thread Jean-Michaël Celerier
I remember asking for the same thing a few weeks ago on IRC because of a small behaviour change in cmake 3.8.0 rc2 that I wanted to put behind an if(version_less). Alphanumeric ordering would certainly work for most projects : alpha < beta < rc. (I generally use a0, a1, a2... b0, b1, b2...) Best

Re: [cmake-developers] Support for version suffixes

2017-03-28 Thread Brad King
On 03/27/2017 05:03 PM, Roger Leigh wrote: > I'd like to bring this issue to your attention to canvas some feedback > regarding the use of version suffixes: > >https://gitlab.kitware.com/cmake/cmake/issues/16716 > > The proposal linked above contains a much more detailed rationale and >

Re: [cmake-developers] Support for version suffixes

2017-03-28 Thread Brad King
On 03/28/2017 04:07 AM, Jean-Michaël Celerier wrote: > I remember asking for the same thing a few weeks ago on IRC because of > a small behaviour change in cmake 3.8.0 rc2 that I wanted to put behind > an if(version_less). For reference, this was also proposed in issue 16656 [1]. The problem is

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-597-gcc4fbda

2017-03-28 Thread Kitware Robot
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 cc4fbda1a9fffd8927de870643f167f066b26bcd (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-591-g645fc9b

2017-03-28 Thread Kitware Robot
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 discards 23929b12ff818429786309261065d03c201a7b87 (commit) discards

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-600-g3b32fdc

2017-03-28 Thread Kitware Robot
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 discards 645fc9b377931fb0df4360eb7a8dff2073394b6b (commit) discards

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc3-12-g85abc5f

2017-03-28 Thread Kitware Robot
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 85abc5f5aa5f8afbca88e7b3e1c919db49756ecb (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-589-g83199f8

2017-03-28 Thread Kitware Robot
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 83199f8daf13328a4fb97c16476c3a0da4228ead (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-602-gbc35c1b

2017-03-28 Thread Kitware Robot
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 bc35c1bb7b1175e79dd8bc177fb47f8367fae26b (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-612-g896e195

2017-03-28 Thread Kitware Robot
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 896e195588bde813ad6e0cc8af7fe1594d37907c (commit) via

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc3-612-g896e195

2017-03-28 Thread Kitware Robot
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, nightly has been updated discards c4c307b8259c39737019ddd1b7d7ce4b5cf89c15 (commit) discards

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc3-597-gcc4fbda

2017-03-28 Thread Kitware Robot
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, nightly-master has been updated via cc4fbda1a9fffd8927de870643f167f066b26bcd (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-598-g3e4e659

2017-03-28 Thread Kitware Robot
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 3e4e6594da5668d7f80a1192594d9ee4fc790eb8 (commit) from

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-613-gae2232a

2017-03-28 Thread Kitware Robot
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 discards 896e195588bde813ad6e0cc8af7fe1594d37907c (commit) discards

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-604-geb3978b

2017-03-28 Thread Kitware Robot
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 eb3978b6688c4233a42b890ebc26e278940942b1 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-610-g10a48e6

2017-03-28 Thread Kitware Robot
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 10a48e620ee872e32642ed5ad1e993776be2a694 (commit) via

Re: [cmake-developers] Some info about AIX needed

2017-03-28 Thread Chuck Atkins
Hi Gregor, Please try to keep these sort of conversations on the dev list to ensure that others can benefit from or contribute to the discussion as well. I just checked on the AIX 7.2 dashboard machine. Here's the output from all possible uname switches described in the manpage: uname -a AIX