On 9/29/2013 2:37 PM, Patrick Reynolds wrote:
I'll leave this one to folks who are better versed in the arcane art of
Bullseye...
Does anyone still use this? ;)
Yes, it is still in use, and no it is not arcane. It is a really good
commercial cross platform branch based coverage tool.
On 9/28/2013 5:36 AM, Rolf Eike Beer wrote:
Break if everything is fine, continue on error or when no files are found? All
other handlers support being run in parallel, why not Bullseye?
Not really.
Return 0 if COVFILE is not set so, no coverage.
Return 0 if COVFILE is set but there was
That was very poor word choice on my part. My apologies. I mean to say:
I leave that to someone more expert in the Bullseye system.
--
Patrick Reynolds
Technical Leader
Kitware, Inc.
919 869 8848
On Monday, September 30, 2013 at 10:32 AM, Bill Hoffman wrote:
On 9/29/2013 2:37 PM, Patrick
Hi all,
Does anyone have access to a HP-UX B.11.31 machine that can run nightly
CMake dashboards?
Thanks.
-Bill
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
Am 30.09.2013 16:45, schrieb Bill Hoffman:
On 9/28/2013 5:36 AM, Rolf Eike Beer wrote:
Break if everything is fine, continue on error or when no files are
found? All
other handlers support being run in parallel, why not Bullseye?
Not really.
Return 0 if COVFILE is not set so, no coverage.
I can't figure out how to generate a start menu that reflects my selection of
installed components.
This is for installation on windows using cmake, cpack and nsis.
Is it possible to do?
Regards
Lars
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
Hello,
I try to use a macro call like find_package(Boost 1.49 REQUIRED COMPONENTS
spirit). But I get surprised by the following messages despite of a complete
installation from the current source files of this software library.
elfring@Sonne:~/Projekte/Bau/boot_parameters/boost cmake .
On 30 September 2013 12:00, SF Markus Elfring
elfr...@users.sourceforge.net wrote:
Hello,
I try to use a macro call like find_package(Boost 1.49 REQUIRED COMPONENTS
spirit).
Boost.Spirit is headers-only library, so there is no binary library supplied.
It might be not obvious from the manual
Boost.Spirit is headers-only library, so there is no binary library supplied.
Thanks for your response.
It might be not obvious from the manual [1], but COMPONENTS is dedicated
to request lookup for the Boost libraries which are built as binary
components.
Can this documentation be
On 30 September 2013 13:58, SF Markus Elfring
elfr...@users.sourceforge.net wrote:
It might be not obvious from the manual [1], but COMPONENTS is dedicated
to request lookup for the Boost libraries which are built as binary
components.
Can this documentation be improved?
I'm sure it can, I
Perhaps, all headers-only libraries could be handled by the FindBoost module
I would appreciate if corresponding CMake scripts will consider a better
handling for such software.
and then reported by CMake:
Spirit is headers-only, shall not be specified with COMPONENTS
I would prefer a
Hello everyonne,
I try to build my lybrary in debug and release mode in only one command.
The purpose is to create a package with the minimum files (library in
debug and release mode and headers) inside it.
Actually, I do something like this:
add_custom_command(OUTPUT
Hi all,
Does anyone have access to a HP-UX B.11.31 machine that can run nightly
CMake dashboards?
Thanks.
-Bill
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
Hi,
I am attempting to compile a library (Dakota) on my Mac workstation,
but the process exits while attempting to create a library from fortran
code in order to test the fortran compiler installation.
The .o file is built without problems, but at the stage when it is supposed
to run the ar
This macro currently doesn't properly match warnings emitted by SunStudio 12.
This patch fixes that.
0001-Added-SunStudio-12-regex-for-CheckCCompilerFlag.patch
Description: Binary data
signature.asc
Description: Message signed with OpenPGP using GPGMail
--
Powered by www.kitware.com
Dear All,
if(${CMAKE_SYSTEM_NAME} MATCHES Linux)
differs from
if(${CMAKE_SYSTEM_NAME} matches Linux)
Is this behavior expected ?
Regards, Sumit
--
Sumit Adhikari,
Senior Architect - Product Development,
Synphony Teleca
--
Powered by www.kitware.com
Please keep messages on-topic and check
Hi Bill,
What's involved in the dashboard? Does the server pull and build or is the
build pushed?
thanks,
Amul
On 09/30/13 11:12, Bill Hoffman wrote:
Hi all,
Does anyone have access to a HP-UX B.11.31 machine that can run nightly CMake
dashboards?
Thanks.
-Bill
_
The
Hi,
I am trying to get dependencies right in a project that uses auto-generated
sources.
I have a library, that uses auto-generated files, and other executables
that use that library.
I created a set of CMakeLists.txt files that show the problem.
To run it you need test.c and org.c in the source
On 9/30/2013 12:26 PM, Amul Shah wrote:
Hi Bill,
What's involved in the dashboard? Does the server pull and build or is the
build pushed?
thanks,
Amul
You setup a cronjob and pull from us. The server does not have any
access to your machine. Basically, a ctest script is run that pulls
It might be confusing -- well it is confusing! -- but CMake built-in
commands, functions and macro names are case insensitive. CMake command
keywords are case sensitive.
The first is a legal CMake command. The second is a fatal CMake error:
CMake Error at CMakeLists.txt:13 (if):
if given
Am Montag, 30. September 2013, 12:58:40 schrieb Jakub Schmidtke:
Hi,
I am trying to get dependencies right in a project that uses auto-generated
sources.
I have a library, that uses auto-generated files, and other executables
that use that library.
I created a set of CMakeLists.txt files
Am Montag, 30. September 2013, 16:15:07 schrieb William Orr:
This macro currently doesn't properly match warnings emitted by SunStudio
12. This patch fixes that.
I guess this also applies to the C++ compiler? Please rebase this change on
the cxx-flags topic on stage where the handling of those
Thanks. This is scary :(
Regards, Sumit
On Mon, Sep 30, 2013 at 10:32 PM, Williams, Norman K
norman-k-willi...@uiowa.edu wrote:
It might be confusing -- well it is confusing! -- but CMake built-in
commands, functions and macro names are case insensitive. CMake command
keywords are case
The workaround I found so far is to add a custom target that depends on the
targets I want to build.
So if I add this:
add_custom_target(test12 DEPENDS test1 test2)
to my CMake file, and instead of running 'make -j test1 test2' I run 'make
-j test12' everything seems to be fine...
On Mon,
I don't see the problem you're having.
I re-wrote your CMakeLists.txt slightly to not use Unix commands:
cmake_minimum_required(VERSION 2.8)
project(Test)
add_custom_command(OUTPUT file.c
COMMAND echo GENERATING FILE
Furthermore gvim adds more confusion to it
On Mon, Sep 30, 2013 at 10:43 PM, Sumit Adhikari
sumit.adhik...@gmail.comwrote:
Thanks. This is scary :(
Regards, Sumit
On Mon, Sep 30, 2013 at 10:32 PM, Williams, Norman K
norman-k-willi...@uiowa.edu wrote:
It might be confusing -- well it
Actually I see the problem now -- it works fine if you build with one job,
but if you run 2 jobs, it for some reason runs the custom command and the
library build command twice.
Which is weird, and probably a bug. Without digging into the generated
Makefiles, it seems like the custom command
I don't know why that is scary. It is the way CMake works, something that
one must accomodate in order to use CMake.
Obviously, if the Kitware people had it to do all over again, they
probably would do some things differently. But CMake has evolved (a lot!)
over the years, and it has some
On Mon, Sep 30, 2013 at 10:29 AM, Williams, Norman K
norman-k-willi...@uiowa.edu wrote:
I don't know why that is scary. It is the way CMake works, something that
one must accomodate in order to use CMake.
I find it scary, annoying, and difficult to learn. If CMake is going to only
behave
On Sep 30, 2013, at 10:14 AM, Rolf Eike Beer e...@sf-mail.de
wrote:
Am Montag, 30. September 2013, 16:15:07 schrieb William Orr:
This macro currently doesn't properly match warnings emitted by SunStudio
12. This patch fixes that.
I guess this also applies to the C++ compiler? Please rebase
On Monday 30 September 2013, Jakub Schmidtke wrote:
The workaround I found so far is to add a custom target that depends on the
targets I want to build.
So if I add this:
add_custom_target(test12 DEPENDS test1 test2)
to my CMake file, and instead of running 'make -j test1 test2' I run 'make
On Sat September 28 2013 8.15.05 PM Clifford Yapp wrote:
On Thu, Sep 26, 2013 at 4:39 PM, Jacky Alciné jackyalc...@gmail.com wrote:
Hey all,
I’ve been working on a Vim plug-in for Cmake. It provides a bit of support
but it’s on the rise and I’d love to hear from the Vim + Cmake users
On Sat September 28 2013 9.50.30 PM Magnus Therning wrote:
On Thu, Sep 26, 2013 at 04:39:06PM -0400, Jacky Alciné wrote:
Hey all,
I've been working on a Vim plug-in for Cmake. It provides a bit of
support but it's on the rise and I'd love to hear from the Vim +
Cmake users about it.
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 73a36cae17a1ff85c4ab65c289222e1d0ef4236e (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 4f3b3f79bb62701b1338de22c1d99758db1d3acd (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 ec046f40850478b2f914650fb154688bfaaca7af (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 fdc5a144f00c0c55410ea8bf9f4002332d82ea47 (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 d821938693a7bd425a810712c56a719e95aba71c (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 92e0db00464f447dbab81d2cf94fec16ba8dcbd8 (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 8b2eb31aa2d35897bd4b88ec4ee26f93cf1ee83f (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 7d1bdc4634f7846c1c716883c45f4e506f6377fe (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 803fd65ef2f5d7b841cc4c4ef66acbf1164f80cd (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 cd5d958fcfd904bc33a4673009fd066f92c457ee (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 ec3a3610ecf97dd539f695b97cf7483d6ff4f208 (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 8f1e31821673570e3ac3297eb07b83afaeacb091 (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index ca78968..1b0177e 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
set(CMake_VERSION_MAJOR 2)
set(CMake_VERSION_MINOR 8)
set(CMake_VERSION_PATCH 11)
-set(CMake_VERSION_TWEAK 20130930
46 matches
Mail list logo
