The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12908
==
Reported By:Christopher Sean Morrison
Assigned
On Fri, Jan 20, 2012 at 3:20 PM, Stephen Kelly steve...@gmail.com wrote:
Hi,
I've force pushed my branch:
https://gitorious.org/~steveire/cmake/steveires-cmake/commits/target-
include-directories
Brad King wrote:
On 1/8/2012 11:47 AM, Stephen Kelly wrote:
On 12/05/2011 03:17 PM, Brad
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12909
==
Reported By:James Mansion
Assigned To:
David Cole wrote:
On Fri, Jan 20, 2012 at 3:20 PM, Stephen Kelly
steve...@gmail.com wrote:
Hi,
I've force pushed my branch:
https://gitorious.org/~steveire/cmake/steveires-cmake/commits/target-
include-directories
Brad King wrote:
On 1/8/2012 11:47 AM, Stephen Kelly wrote:
On
The documentation you get from
cmake --help-full
refers to the IMPORTED_LOCATION property as one of the more important
ones set for imported targets. I have to agree that location is the
most important property for imported targets, but the name appears to
be wrong for the documentation of
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12910
==
Reported By:Andreas Schuh
Assigned To:
On Saturday, 21. January 2012, 22:51:01, Oliver Smith wrote:
I have a script that generates a revision.h file, I've spent the morning
trying to figure out how to make it so that ... any time CMake rebuilds
any of the other targets, it starts by running the make-new-revision
script.
The idea
I want to force all the install permissions to be only owner
accessible. I've done this everywhere using DIRECTORY_PERMISSIONS and
FILE_PERMISSIONS. But, intermediate directories created by installing
targets get some default permissions (in my case, 0755).
I don't want to require the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I do not know if it is too late to require bugfix for the next release
or even whether this bug is known (a quick browsing of buzilla shows
nothing and the git sources still contain the bug), but in any case.
In cmake-2.8.6, the module
It's a bit tricky to follow the code, but from my first attempt with the
debug symbols activated I get the following backtrace:
(running cpack -G NSIS)
--8---cut here---start-8---
(gdb) bt
#0 0x76e28935 in raise () from /lib/libc.so.6
#1
Hi,
I have a CTest script that builds many different tests and sets it to APPEND by
doing:
foreach(TESTCASE ${LESLIE_AVAILABLE_TESTCASES})
set(CTEST_CONFIGURE_COMMAND ./setup.py -t ${TESTCASE}
'{${LESLIE_CONFIGURE_DICT_BASE}}')
ctest_configure(BUILD ${CTEST_REPO_DIRECTORY} APPEND)
Hi,
I have been asked to run our ctest regression suite on a machine that is
heavily firewalled. This means that I cannot use 'ctest_submit()' from my
ctest script to post the results to our CDash web site. Through some script
magic I can move the CTest xml files to a machine that can see
Theodore Papadopoulo wrote:
I do not know if it is too late to require bugfix for the next release
or even whether this bug is known (a quick browsing of buzilla shows
nothing and the git sources still contain the bug), but in any case.
In cmake-2.8.6, the module FindLAPACK.cmake contains
On Mon, Jan 23, 2012 at 12:45 PM, Tim Gallagher
tim.gallag...@gatech.edu wrote:
Hi,
I have a CTest script that builds many different tests and sets it to APPEND
by doing:
foreach(TESTCASE ${LESLIE_AVAILABLE_TESTCASES})
set(CTEST_CONFIGURE_COMMAND ./setup.py -t ${TESTCASE}
Hi Roland,
have you considered writing a CTest script which you would run as follows:
ctest -S your_script.ctest
?
In your CTest script, you can use the commands
ctest_start()
ctest_configure()
ctest_build()
set (CTEST_MEMORYCHECK_COMMAND_OPTIONS ...)
ctest_memcheck() where you include only
On Mon, Jan 23, 2012 at 2:26 PM, Andreas Schuh
andreas.schuh...@googlemail.com wrote:
Hi Roland,
have you considered writing a CTest script which you would run as follows:
ctest -S your_script.ctest
?
In your CTest script, you can use the commands
ctest_start()
ctest_configure()
From issue 12909: (rc.exe cannot find generated type library, Visual
Studio 10 builder)
I have an IDL file that generates a type library, and an RC file that
wants to embed it.
The .tlb is emitted here:
C:\build\easyrtd.vs10\EasyRTD\easyrtd.dir\Debugdir *.tlb
Volume in drive C has no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2012 07:29 PM, Rolf Eike Beer wrote:
Theodore Papadopoulo wrote:
I do not know if it is too late to require bugfix for the next
release or even whether this bug is known (a quick browsing of
buzilla shows nothing and the git sources still
On Sunday 22 January 2012, Alfa Omega wrote:
Hi everyone,
I'm not quite sure what the correct procedure is for becoming a CMake
contributor, but from what I've read I should send a email here if I want
to add a new module to cmake.
For the past year I've been hosting my CMake modules on
Hi,
I wish to package up a collection of dylibs, python scripts and a
starter shell script as a MACOSX_BUNDLE
E.g. given a file startup.sh
Is there some way to do something like (but as a MACOSX_BUNDLE)
add_executable ( STARTUP_SCRIPT IMPORTED IMPORTED_LOCATION
Hi,
Setting CTEST_EXTRA_COVERAGE_GLOB in the CTestCustom.cmake file can be
used to add additional files which shall be included in the coverage
report. This is useful to ensure that files which are not covered by
any test are still reported with 0% line coverage.
I tried using absolute paths in
As you know, in target_link_libraries(), you can specify debug,
optimized, or general to specify which configurations a library will be
applied to.
I have developed a system to allow dependencies to recursively add their
own dependencies. Suppose we have 3 targets:
A:
libx
liby
libz
B:
Hello,
I'm doing an application for Debian based systems and I need to package
a .deb file, my application has several files to install in addition to
the main executable.
So, my CMakeLists.txt file looks like:
project(myapp C)
cmake_minimum_required(VERSION 2.8)
# The executable
Hi,
What part does not follow the convention? I'm using a toolchain file, plus
when I was writing this I based it on a existing module bundled with CMake
(but cant remember which).
I'm open to modifying my project to match the convention. If you could
point out which parts don't quite meet the
On 01/21/2012 10:51 PM, Oliver Smith wrote:
I have a script that generates a revision.h file, I've spent the morning
trying to figure out how to make it so that ... any time CMake rebuilds
any of the other targets, it starts by running the make-new-revision script.
The idea is, I use the
My component source list includes:
easyrtd.src/COMRtdInterface.cpp
easyrtd.src/EasyRTD.rc
easyrtd.src/EasyRTD.idl
and after fixing up the paths Visual Studio builds the project OK.
However, nmake does not - the RC compiler runs before MIDL.
It seems that there is a dependency
2012/1/24 Damián Nohales damiannoha...@gmail.com:
Hello,
I'm doing an application for Debian based systems and I need to package
a .deb file, my application has several files to install in addition to
the main executable.
So, my CMakeLists.txt file looks like:
project(myapp C)
Hi Alfa,
We are really interested in the teamcity + CTest support. Is that available
somewhere already?
Thanks
/Johan
On Sun, Jan 22, 2012 at 7:51 PM, Alfa Omega queezythegr...@gmail.comwrote:
Hi everyone,
I'm not quite sure what the correct procedure is for becoming a CMake
contributor,
Andreas Schuh wrote:
Hi,
Setting CTEST_EXTRA_COVERAGE_GLOB in the CTestCustom.cmake file can be
used to add additional files which shall be included in the coverage
report. This is useful to ensure that files which are not covered by
any test are still reported with 0% line coverage.
Oh,
2012/1/24 Rolf Eike Beer e...@sf-mail.de:
Andreas Schuh wrote:
Hi,
Setting CTEST_EXTRA_COVERAGE_GLOB in the CTestCustom.cmake file can be
used to add additional files which shall be included in the coverage
report. This is useful to ensure that files which are not covered by
any test are
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 6d403e168707cbdbf81bcb503de07a0a56770ea3 (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 85200d8e6e841d94e53674025cadb6a1ed857c53 (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 f9ed351ea5313cef177de225ffcec506702844b5 (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 fac20b8adb0a9aa338e670957f62eadf756ecc69 (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 a6810c3c5cb8e0a83bac551c36b5312909f48a8b (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 42dd02e12064aa642ce83aa02c3c0d8a0cd4424b (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 99180a0bb27eefd6ef8802c8d5c26a2f6e1cec68 (commit)
from
37 matches
Mail list logo
