[CMake] Patch for Sphinx warning message

2015-07-13 Thread Andrew Maclean
This patch fixes this warning when building CMake from the master: "WARNING: 'default' html theme has been renamed to 'classic'. Please change your html_theme setting either to the new 'alabaster' default theme, or to 'classic' to keep using the old default." It ensures that the "classic" theme is

Re: [CMake] Problem with CMake 3.3.0-rc3

2015-07-13 Thread Clifford Yapp
On Sat, Jul 11, 2015 at 5:07 AM, Stephen Kelly wrote: > Brad King wrote: > >> Steve, please take a look. It looks like the cmState methods >> RemoveUserDefinedCommands and RenameCommand need to work better >> together. This needs to be fixed for 3.3. > > Fixed with > > http://www.cmake.org/gitw

Re: [CMake] Is there any way to set a build-type specific install path for multiconfig tools?

2015-07-13 Thread J Decker
On Mon, Jul 13, 2015 at 10:45 AM, David Cole via CMake wrote: > A few more ideas: > > > The other "no need to modify CMake" way to achieve this (although it > may be considered "too ugly" or non-ideal by some) would be to force > the use of a single configuration per build tree, and use the prope

[CMake] [ANNOUNCE] CMake 3.3.0-rc4 is now ready!

2015-07-13 Thread Robert Maynard
I am proud to announce the fourth CMake 3.3 release candidate. Sources and binaries are available at: http://www.cmake.org/download/ Documentation is available at: http://www.cmake.org/cmake/help/v3.3 Release notes appear below and are also published at http://www.cmake.org/cmake/help/v3.3

Re: [CMake] Can't find wxWidgets

2015-07-13 Thread Bob Bachman
Richard Shaw writes: > > On Thu, Jul 9, 2015 at 3:09 PM, Bob Bachman wrote: > It's defined in the CMakeLists.txt file and stored in the CMakeCache.txt > file. > //Path to a program. > wxWidgets_CONFIG_EXECUTABLE:FILEPATH=/home/mzx_bldr/mozaix_svn/engineering/c > ommon_src/src/wxWidgets-3.0.2/b

Re: [CMake] Is there any way to set a build-type specific install path for multiconfig tools?

2015-07-13 Thread David Cole via CMake
A few more ideas: The other "no need to modify CMake" way to achieve this (although it may be considered "too ugly" or non-ideal by some) would be to force the use of a single configuration per build tree, and use the proper value for CMAKE_INSTALL_PREFIX in each build tree. Your developers may

Re: [CMake] Fwd: Re: Re: opening files relative to cmake build directory

2015-07-13 Thread Micha Hergarden
In that case you can disregard my first reply. If it is a file to be used at runtime, then I would use file(COPY ...) or install() to export the recources.txt from your source directory to your build directory. Then you will have a flexible way that will also work in other setups. It may seem waste

[CMake] Fwd: Re: Re: opening files relative to cmake build directory

2015-07-13 Thread Micha Hergarden
Forwarded Message Subject:Re: Re: [CMake] opening files relative to cmake build directory Date: Mon, 13 Jul 2015 17:00:52 + From: Owen Alanzo Hogarth To: Micha Hergarden Resources.txt is a test but it's mainly going to be used for assets at runtime. May

Re: [CMake] opening files relative to cmake build directory

2015-07-13 Thread Micha Hergarden
On 07/12/2015 02:14 PM, Owen Alanzo Hogarth wrote: > I have a little project that's setup like this > > project > main.c > build > resources > source > .../module1 > .../module2 > .../etc > > main.c loads dynamic libs from under the source folder. > > I am trying to open up a file using c fopen > >

[CMake] file(GENERATE) and executable permissions

2015-07-13 Thread James Bigler
Is it possible to set the generated file's executable permissions when using file(GENERATE)? I'm trying to generate shell scripts, and I want the executable bit set. Thanks, James -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki

Re: [CMake] Is there any way to set a build-type specific install path for multiconfig tools?

2015-07-13 Thread Clifford Yapp
On Mon, Jul 13, 2015 at 12:05 PM, David Cole wrote: > I think this should be achievable somehow with CMAKE_INSTALL_PREFIX > set to "/parent_dirs" and then using appropriate DESTINATION and > CONFIGURATIONS arguments to the CMake install commands. > > Have you tried using the CONFIGURATIONS args to

Re: [CMake] Is there any way to set a build-type specific install path for multiconfig tools?

2015-07-13 Thread David Cole via CMake
I think this should be achievable somehow with CMAKE_INSTALL_PREFIX set to "/parent_dirs" and then using appropriate DESTINATION and CONFIGURATIONS arguments to the CMake install commands. Have you tried using the CONFIGURATIONS args to the install command? On Mon, Jul 13, 2015 at 10:26 AM, Cli

[CMake] Is there any way to set a build-type specific install path for multiconfig tools?

2015-07-13 Thread Clifford Yapp
One challenge we've experienced with CMake is properly controlling the installation path when using multi-config tools like Visual Studio or Xcode. Since I'm in the middle of re-examining our more gnarly CMake logic anyway, I thought I'd raise this one and see if anybody knows of a good solution.

Re: [CMake] Can't find wxWidgets

2015-07-13 Thread Bob Bachman
Richard Shaw writes: > > On Thu, Jul 9, 2015 at 3:09 PM, Bob Bachman wrote: > It's defined in the CMakeLists.txt file and stored in the CMakeCache.txt > file. > //Path to a program. > wxWidgets_CONFIG_EXECUTABLE:FILEPATH=/home/mzx_bldr/mozaix_svn/engineering/c > ommon_src/src/wxWidgets-3.0.2/b

Re: [CMake] Finding internal libraries

2015-07-13 Thread Petr Kmoch
Hi John. I have no first-hand experience with it, but I believe the ExternalProject module could be just what you're looking for ( http://www.cmake.org/cmake/help/v3.2/module/ExternalProject.html ). It allows you to configure and build several projects at build time under a CMake "superbuild" mast