The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15167
==
Reported By:kurt.dupont
Assigned To:
On 09/20/2014 09:57 PM, Tobias Hunger wrote:
Hello!
Sorry for breaking the threading, I only joined this ML just now to
comment on this thread:-) Thanks Stephen for pointing me here!
I am not a regular cmake user (used to be a couple of years ago), but
I im interested in this topic since I
Nils Gladitz wrote:
Might be nice for platforms where RPATHs aren't supported (e.g. Windows)
though a generic, non IDE specific solution might be preferable:
The proposed ProjectTargets.json isn't particularly IDE specific. That's
only the motivation.
Thanks,
Steve.
--
Powered by
On 09/22/2014 03:39 PM, Stephen Kelly wrote:
Nils Gladitz wrote:
Might be nice for platforms where RPATHs aren't supported (e.g. Windows)
though a generic, non IDE specific solution might be preferable:
The proposed ProjectTargets.json isn't particularly IDE specific. That's
only the
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15168
==
Reported By:dhardy
Assigned To:
Tobias Hunger wrote:
The first is should this be run in a terminal or is this a GUI. Not
sure whether cmake has that information.
CMake only knows whether the WIN32_EXECUTABLE property has been set on a
target.
http://www.cmake.org/cmake/help/v3.0/prop_tgt/WIN32_EXECUTABLE.html
The
On 09/19/2014 06:07 PM, Taylor Braun-Jones wrote:
On Fri, Sep 19, 2014 at 3:04 PM, Brad King wrote:
I think it can be activated by a special format of an entry in
ExternalData_URL_TEMPLATES that specifies a lookup key that maps
to some kind of custom configuration of a .cmake script to include
On 09/21/2014 12:45 PM, Adam Strzelecki wrote:
I have pushed new branch stage/compact-status-log for review.
Neat.
Idea behind is to reduce cmake output when we are in terminal.
When we are outputting message Trying feature we can later
remove it when new output comes using ANSI escape
On 09/20/2014 09:18 AM, Stephen Kelly wrote:
I don't know why I added it.
There is also a 'new'
+location += /;
in that patch further down which might be removable.
Thanks for pointing that one out too. I've removed both with a
commit message that explains one hypothesis as to why
On 09/21/2014 02:48 PM, Adam Strzelecki wrote:
FYI unfortunately this solution does not work for CMakeFiles.txt
with cmake_minimum_required(VERSION 2.6.1) or earlier because of
CMP0011 that does implicit PUSH/POP does not work there. So
setting cmake_policy(SET CMP0054 NEW) is internal modules
Thanks. I split that into two commits with slight edits, and added
my own commit to add subsections for Windows Phone and Store:
Help: Add Cross Compiling subsections in cmake-toolchains.7 manual
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0d72451a
Help: Add Windows CE
---
Source/cmVisualStudio10TargetGenerator.cxx | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/Source/cmVisualStudio10TargetGenerator.cxx
b/Source/cmVisualStudio10TargetGenerator.cxx
index 4b5c83f..e0a32a2 100644
--- a/Source/cmVisualStudio10TargetGenerator.cxx
On 09/22/2014 10:19 AM, Pascal Bach wrote:
---
Source/cmVisualStudio10TargetGenerator.cxx | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
VS, WINCE: Only set EntryPointSymbol for executables
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e7aeb79f
Thanks,
-Brad
--
On Mon, Sep 22, 2014 at 10:07 AM, Brad King brad.k...@kitware.com wrote:
Perhaps:
list(APPEND ExternalData_URL_TEMPLATES
ExternalDataCustomScript://MyFetch/%(algo)/%(hash)
)
set(ExternalData_CUSTOM_SCRIPT_MyFetch /path/to/MyFetch.cmake)
The script would be include()-ed in
Please see last comment at
http://public.kitware.com/Bug/view.php?id=15166
-- Original Message --
Date: September 1, 2014 at 2:35 PM
Subject: Re: [cmake-developers] How to get a nightly build process
going.
Back on topic...
Solaris 10 + SolarisStudio
What if stdout's buffer happens to fill up and flush anyway?
I think I can provide other terminal-less solution via filtering stdout and
stderr via pipe and background thread.
I got some proof-of-concept program already. Idea is:
stdout stderr are duped and proxied by some background thread.
On 09/22/2014 12:26 PM, Adam Strzelecki wrote:
stdout stderr are duped and proxied by some background thread.
IMO that is too much infrastructure to solve what is essentially
a cosmetic problem.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
On 09/22/2014 12:08 PM, dev wrote:
Please see last comment at
http://public.kitware.com/Bug/view.php?id=15166
[snip]
Your nightly process needs to have mercurial around it seems and not
subversion or git which I have.
Only git is needed. If hg or svn is available some extra tests
are
IMO that is too much infrastructure to solve what is essentially
a cosmetic problem.
Well, IMHO it is usability problem, because cmake emits simply too much
(redundant) information.
FYI I have pushed new stage/compact-status-log which does include this
automatic subsequent status log line
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15169
==
Reported By:Sam Hartsfield
Assigned To:
On Fri, Sep 19, 2014 at 7:44 PM, Brad King brad.k...@kitware.com wrote:
On 09/18/2014 08:10 PM, Aleix Pol wrote:
I added a CMAKE_OUTPUT_PROJECT_TARGETS variable that can be used to
enable the generation of the file.
I also renamed the file to ProjectTargets.json.
Please install cmake bash_completion and then it will be easy as typing: cmake
-Dtab
--Adam
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
Has anyone used CMake for VxWorks environments?
As far as I can see, there is no VxWorks support yet in the cmake distribution.
The cleanest way seems to create a VxWorks.cmake in the Modules/Platform
directory that specifies the OS specifics.
Also a create a file VxWorks-toolchain.cmake that
Well, it depends on who you are expecting the user to be and what their
background is. I always configure new cmake buiulds with cmake-gui or
ccmake, which I find to be much easier than auto tools, because the
documentation and ability to set options is in the same place--one stop
shopping. No
Kitware is hosting a CMake training course, titled “Project Lifecycle
Management with the CMake Family of Tools,” in Carrboro, NC. The course
will be held on October 20, 2014. Through the course, you will learn how
to create a build system for your C/C++/Fortran project using CMake,
CPack,
Hi,
CMake has graphviz output capability for dependency within a project.
Is there a way to graph dependency at the ExternalProject_Add() level ?
Cheers
--
Nicholas Yue
Graphics - RenderMan, Visualization, OpenGL, HDF5
Custom Dev - C++ porting, OSX, Linux, Windows
On 9/22/2014 1:45 AM, Cristian Adam wrote:
On QNX side, thins are not as good. First, in order to compile
the project I had to apply this patch [1], provided by Stephen Kelly.
And now the fail part for QNX, the second subsequent build
doesn't say ninja: no work to do instead it starts
On Mon, Sep 22, 2014 at 5:40 PM, Bill Hoffman bill.hoff...@kitware.com
wrote:
On 9/22/2014 1:45 AM, Cristian Adam wrote:
On QNX side, thins are not as good. First, in order to compile
the project I had to apply this patch [1], provided by Stephen Kelly.
And now the fail part for QNX, the
Hello,
The build tool CMake supports also the data processing for lists to some
degree.
http://www.cmake.org/cmake/help/v3.0/manual/cmake-language.7.html#lists
I notice that CMake scripts are also provided by some software libraries so that
corresponding settings can be automatically determined
We have some semaphore code that has conditional compilation based on
#defines in config.h. We're having problems with resolving the various
PTHREAD_* symbols to get the correct values in config.h. Our first attempt
at this (done on Linux) used
check_symbol_exists(PTHREAD_MUTEX_RECURSIVE
Hello! I am trying to build my Dashboard targets from inside Xcode, and it
keeps failing! Here is the build log...
echo
/usr/local/Cellar/cmake/3.0.2/bin/ctest -C Debug -D Experimental
Site: macpat
Build name: Darwin-clang++
Create new tag: 20140922-1554 - Experimental
Configure project
On 9/22/2014 11:53 AM, Cristian Adam wrote:
-d explain parameter gives for lots of files (probably all) in the
project (headers, source files, object files, static libraries,
executables)
is dirty
This means that ninja's method of detecting if a file has been changed
doesn't quite work for
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 e8ae79ef2e865978910400dcdb3f6024fe62747f (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 5eaa3e90255c8ff8a54e300dd336e0b09f75a2d3 (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 d4713b84b70ffc7da81f8b247f943fa93bd5899f (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 e6f0bb7b1577923b6252370a6c8dd2db202dece7 (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 2f3985c6a5c35f53301762fe74cf83213a29afd0 (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 3303b5f8b462d12af3874cee1b97fabfee6ffb3e (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 d8dde37d609fd0badfa4c9d13c927c2d2ed27902 (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 f28ebcbf1b59fad51833aead76e4f733d7292503 (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 6771c0bbdbfcbcf2a217118f28162918e969bfc5 (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 0ab2718448fbcdd1f85b76a7186b65a818a5cd1c (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 2b1b1b1cfaf88d494175b44f3c5b17d4c0842dd7 (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 405b92d031176b1475e2ad9f793c9087484bc86d (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 829e9eca04026cd51fa4f419b0d2a77522a010fa (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 21fb60b7b6171c340ea432968950729e329cb4c8 (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 9d10a8223e96a7bc54b56a3f7c2dd8a8169ed297 (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 c58a90cde0fb09899c7999cc89ea6145edc2ff15 (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 2b3ce8341c1d4862f20a798746c128ddac1ad540 (commit)
via
20140922)
+set(CMake_VERSION_PATCH 20140923)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
50 matches
Mail list logo
