This didn't sink in:, but now I get it.
As it is, cmake on windows doesn't get the mounting of /usr
The MSYS soft mount is a feature of the MSYS shell. It maps
such paths in command lines to the corresponding Windows paths.
No other programs are expected to translate such paths.
Now
On 05/19/2014 07:42 PM, Brad King wrote:
On 05/16/2014 04:56 PM, Nils Gladitz wrote:
I write the properties file at generation time rather than configuration
time ... perhaps generator expressions could be allowed for keys?
So far generator expressions are allowed only when the content will
I'm seeing some build problems show up on cdash from some of my builds that use
ninja.
The error that shows up on cdash is:
ninja: error: GetFileAttributesEx(c:\Program Files (x86)\Mcl : Command line
warning D9025 : overriding ): The filename, directory name, or volume label
syntax is
On 05/20/2014 04:19 PM, clin...@elemtech.com wrote:
I'm not sure if cmcldeps can be changed to ignore stderr, or if
kwsysProcess needs fixed to alternately read stderr/stdout in the order
the child process printed to them. I imagine the latter might be
possible if the same HANDLE was given to
On 05/20/2014 10:19 AM, clin...@elemtech.com wrote:
when cmcldeps calls cmSystemTools::RunSingleCommand(),
the stderr and stdout are merged inconsistently.
[snip]
I'm not sure if cmcldeps can be changed to ignore stderr
KWSys.Process does treat stdout/stderr separately and has
many options to
On Tuesday, May 20, 2014 05:53:16 PM Rolf Eike Beer wrote:
Clinton, Stephen,
inspired by what OpenBSD currently does downstream I did a patch that always
searches for the plain executable names (like moc) after all versioned
executable names (e.g. moc4) have been tried. Since those tools are
Assuming USE_FOLDERS is set [0], does set_property( TARGET test_swig
PROPERTY FOLDER PYTHON ) work?
[0] http://www.cmake.org/cmake/help/v2.8.12/cmake.html#prop_global:USE_FOLDERS
On Fri, May 16, 2014 at 4:45 PM, Giumas giu...@yahoo.it wrote:
Good morning,
I am working for the first time with
On 05/20/2014 08:36 AM, Iosif Neitzke wrote:
Assuming USE_FOLDERS is set [0], does set_property( TARGET test_swig
PROPERTY FOLDER PYTHON ) work?
From the documentation:
To get the name of the swig module target library, use:
${SWIG_MODULE_${name}_REAL_NAME}
So perhaps:
set_property(TARGET
On 05/20/2014 11:46 AM, Michael Jackson wrote:
C:\Users\mjackson\Workspace\CTEMsoft\x64\CMakeFiles\CMakeTmp\cmTryCompileExec1754897950.vfproj(2,1):
error MSB4075: The project file
C:\Users\mjackson\Workspace\CTEMsoft\x64\CMakeFiles\CMakeTmp\cmTryCompileExec1754897950.vfproj
must be opened in
CMake-Gui Crashes and Cmake on the command line gives this error:
C:\Users\mjackson\Workspace\CTEMsoft\x64C:\Applications\cmake-3.0.0\bin\cmake -
G Visual Studio 12 2013 Win64 ../
CMake Error: Could not find CMAKE_ROOT !!!
CMake has most likely not been installed correctly.
Modules directory not
You need to set the install_name of the libHello.dylib so that the Bundle
Script can find the library properly and fix those internal install_name
entries.
Mike Jackson
On May 13, 2014, at 8:32 AM, Romain LEGUAY romain.leg...@gmail.com wrote:
Hello everyone,
I try to build a small Qt
So the issue was that I downloaded the .zip for the CMake 3.0 installer, then
unzipped, then renamed the resulting directory to something a bit shorter. That
caused problems. Just unzipping in the downloads directory and running CMake
from there allowed my Intel Visual Fortran project to
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 ab07b2dd4febe0d862654a08ac2c68a3844b919c (commit)
via
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 c1edede31f4e979826a5fc0f6e56b1b59cb00f21 (commit)
via
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 d01320d4b74dfa51952499f28974b764ae63b0f8 (commit)
via
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 2d5e3d2d2bfd79311c40db173d13f6d0cfb10019 (commit)
via
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 9af375b3affa817e905a6ad4b373d0b9b500dc96 (commit)
via
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 8519fd6ab067c0853f99f7f63ba76c56469503df (commit)
via
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 fe7e36a8b3e98a1d0575f4e27952d50783ada53d (commit)
via
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 4bb54f7ace4fb3a46358d730c9c3f9d03411d649 (commit)
via
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 5c7802af9934ce270a4ddc016c193504983976ac (commit)
via
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 f83aa55ad7666581ea5ff65ba40ab95ba47d6b3f (commit)
via
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 44d327ffd19d6cfe984a426aa4ba71fe65e66e77 (commit)
via
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 f0520efb0eb04e103cf3f21f5f7a2ee723f44782 (commit)
via
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 dd4da6510ce6be10a858dfc80814ba47316eacc9 (commit)
via
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 e170331314b76bd0121ae9cd504d5f44d8367603 (commit)
via
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 8ddfc5697514fdb55bbb3e3b1b9b684926572d4c (commit)
via
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 1b8164e385cc4c14a06933874e4ffc765a9bdf19 (commit)
via
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 9ffbf6e066a01e8bba90bb237c4177de435128c1 (commit)
via
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 62b0c58a5b21c662cbc62197aa8de163a5e89c40 (commit)
via
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 220e523425aa297bbbd2afad2b630d9c73f8c920 (commit)
via
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 a0c533f27dd8bcb7fbfc9521de5b25ac7f12a738 (commit)
via
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 2bcdb80ed7e68afc491dd752b4847818dafdba46 (commit)
via
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 5ff359aa44572a4e99336c71ebe5ac53e337235a (commit)
via
20140520)
+set(CMake_VERSION_PATCH 20140521)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
35 matches
Mail list logo
