On 1/12/2012 5:47 PM, Rolf Eike Beer wrote:
But I'm not going to add support for things older than 0.9.6, this
stuff is ancient.
Okay, thanks.
Also, the examples given in the header are confusing because they
leave out the patch level from the string. I think the patch level
can be included
On 1/12/2012 6:12 PM, Rolf Eike Beer wrote:
the patch level
can be included as a fourth component in our OPENSSL_VERSION var.
Or just put the normal OpenSSL version string in there? It works for
VERSION_LESS and friends. And since FIND_PACKAGE() handles version selection
anyway I don't see
On 1/13/2012 9:47 AM, Rolf Eike Beer wrote:
On 1/13/2012 9:41 AM, Rolf Eike Beer wrote:
Status = f - this is a released version
PP = 0x1 - a
That doesn't appear in my version. I guess they added it later.
No, indeed exactly the lines you quoted before. It's just that the patch
level is
On 1/13/2012 9:47 AM, Rolf Eike Beer wrote:
On 1/13/2012 9:41 AM, Rolf Eike Beer wrote:
Status = f - this is a released version
PP = 0x1 - a
That doesn't appear in my version. I guess they added it later.
No, indeed exactly the lines you quoted before. It's just that the patch
level
Hi,
We're trying to configure our nightly builds of CMake, ITK, and VTK to submit
coverage reports to the official dashboard (in addition to the compilation and
unit test reports that we already do).
We are building on Mac OS X and use the clang compiler.
While compilation and unit testing
Hi,
A friend of mine has asked me to confirm if there may be a bug in CMake
related to file permissions on Unix. Here is the story:
There are some files under CMakeFiles/ directory owned by root
and not overridable by strk (non-root user).
Having such setup results in a pretty funny behaviour:
On Fri, Jan 13, 2012 at 5:48 AM, Mateusz Loskot mate...@loskot.net wrote:
Hi,
A friend of mine has asked me to confirm if there may be a bug in CMake
related to file permissions on Unix. Here is the story:
There are some files under CMakeFiles/ directory owned by root
and not overridable by
On 13 January 2012 11:30, David Cole david.c...@kitware.com wrote:
On Fri, Jan 13, 2012 at 5:48 AM, Mateusz Loskot mate...@loskot.net wrote:
A friend of mine has asked me to confirm if there may be a bug in CMake
related to file permissions on Unix. Here is the story:
There are some files
On 01/10/2012 07:09 PM, Óscar Fuentes wrote:
Michael Hertling mhertl...@online.de
writes:
But aren't the issues related at least?
Dunno.
If I understand
correctly, cmake --build invokes MSBuild which
- loads the solution file and the project files,
- reinvokes CMake via the
On 1/13/2012 9:10 AM, Michael Hertling wrote:
With CMake 2.8.7 and VS 2008, I can report the following findings:
(1) Starting out from within an empty build directory: cmake ..
followed by cmake --build . configures/builds as expected.
(2) Tweaking CMakeLists.txt file only and leaving
On 1/13/2012 6:41 AM, Mateusz Loskot wrote:
David Daniel, thanks!
I'll confirm with my friend and follow-up if needed.
Best regards,
My guess would be that someone did a sudo make install. That would be a
reason why you might run make a root. But, you have to be consistent
and always
On 01/12/2012 10:23 PM, Robert Dailey wrote:
I see there is documentation for this but it doesn't have an implementation
for VS generators:
http://www.cmake.org/Bug/view.php?id=5811
Any status updates on this bug? I'd like to be able to create my own debug
configuration called DebugStatic
Thanks.
regards
Vivek Goel
On Wed, Jan 11, 2012 at 6:26 PM, Michael Wild them...@gmail.com wrote:
On 01/11/2012 01:44 PM, Michael Hertling wrote:
On 01/10/2012 07:17 PM, vivek goel wrote:
Is there a way to color warning/error of gcc with cmake ?
AFAIK, no, but you might remember the
On Fri, Jan 13, 2012 at 10:22 AM, Michael Hertling mhertl...@online.de wrote:
On 01/12/2012 10:23 PM, Robert Dailey wrote:
I see there is documentation for this but it doesn't have an implementation
for VS generators:
http://www.cmake.org/Bug/view.php?id=5811
Any status updates on this bug?
Hi,
I'm using the Intel Compiler v12 and to have a robust build generator,
before adding flags to CFLAGS I test them.
The following buggy behavior exists in CMake up to v2.8.7:
- As Intel issues
icc: command line warning #10006: ignoring unknown option '-asdf'
type warnings which are not
On Fri, 13 Jan 2012 17:54:23 +0100, Szilárd Páll said:
Additionally, IMHO it's quite unfortunate that such a widely used
compiler as the Intel Compiler has such flaky support in CMake.
Searching today's dashboard for icc, I see only 1 entry:
http://www.cdash.org/CDash/index.php?project=CMake
On Fri, Jan 13, 2012 at 12:23 PM, Sean McBride s...@rogue-research.com wrote:
On Fri, 13 Jan 2012 17:54:23 +0100, Szilárd Páll said:
Additionally, IMHO it's quite unfortunate that such a widely used
compiler as the Intel Compiler has such flaky support in CMake.
Searching today's dashboard for
On 01/13/2012 03:42 PM, Bill Hoffman wrote:
On 1/13/2012 9:10 AM, Michael Hertling wrote:
With CMake 2.8.7 and VS 2008, I can report the following findings:
(1) Starting out from within an empty build directory: cmake ..
followed by cmake --build . configures/builds as expected.
(2)
Hi,
We have a test case suite setup to run in continuous mode and submit to CDash.
I followed instructions on the wiki
(http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest#Continuous_Builds_.28new_Style.29)
and have a script that's below the signature.
I was under the impression that
On Fri, Jan 13, 2012 at 6:23 PM, Sean McBride s...@rogue-research.com wrote:
On Fri, 13 Jan 2012 17:54:23 +0100, Szilárd Páll said:
Additionally, IMHO it's quite unfortunate that such a widely used
compiler as the Intel Compiler has such flaky support in CMake.
Searching today's dashboard for
See the cmake_common.cmake script (as seen here on a CMake Continuous
dashboard, and in other places):
http://cdash.org/CDash/viewNotes.php?buildid=1911520
Notice that it does:
ctest_update(RETURN_VALUE count)
and then checks whether count is 0 or not. It only does stuff if
count 0 or
The devil is always in the little details. That does the trick nicely, thanks!
Tim
- Original Message -
From: David Cole david.c...@kitware.com
To: gtg0...@mail.gatech.edu
Cc: cmake@cmake.org
Sent: Friday, January 13, 2012 2:37:29 PM
Subject: Re: [CMake] CTest continuous testing
See the
2011/4/27 Eric Noulard eric.noul...@gmail.com:
2011/4/27 Daniel Nelson tor...@connect2.com:
On Wed, Apr 27, 2011 at 08:49:56PM +0200, Eric Noulard wrote:
2011/4/27 Daniel Nelson tor...@connect2.com:
I am using CPACK_ARCHIVE_COMPONENT_INSTALL to create separate tar files
for each component,
Is there a CMake variable for the GCC compiler version if using GCC? I
thought I remember seeing email traffic about something along these lines a
while back, but I can't find the email or documentation describing it (if
it exists).
Thanks,
James
--
Powered by www.kitware.com
Visit other
Brad's recently committed and merged to next a topic that does just that.
See the commits in this view:
gitk
e0bc42aa4ff086e9c6976ab91ba924530df0bf72..0df1942a72f1e67c88f0d02dc405fbd76793347a
If you are using next, you can inspect the variables
CMAKE_C_COMPILER_VERSION and
Hi,
I'm using CMake 2.8.6 to generate an NSIS installer. We have two
separate projects; an application and a set of plugins to be used by
the application. The plugins are composed of four separate components
that can be selected during the installation (Filters, NonBSDPlugins,
Readers, Writers).
2012/1/13 Patrick Ryan pr...@objectivity.ca:
Hi,
I'm using CMake 2.8.6 to generate an NSIS installer. We have two
separate projects; an application and a set of plugins to be used by
the application. The plugins are composed of four separate components
that can be selected during the
On 01/13/2012 05:06 PM, David Cole wrote:
On Fri, Jan 13, 2012 at 10:22 AM, Michael Hertling mhertl...@online.de
wrote:
On 01/12/2012 10:23 PM, Robert Dailey wrote:
I see there is documentation for this but it doesn't have an implementation
for VS generators:
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 4992dfa97dadfba618992a4c57270fb6b5d501e9 (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 2ee866a2320722c485a1244163f9d7183b5e6d01 (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 19c85b6c73f4274fd890b9c6f072010fb7c8c678 (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 3eb481524b5c7e4fdbd668431576ff912756e226 (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 ec9d4011a86b18e807aaca65f9a1a93a92ef8c96 (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 c121f3f5c4b874910ab8e5b083827d9e393e1a96 (commit)
from
34 matches
Mail list logo
