Ok, I got this working, but the only way I could get it to work is to use the
configure_file. For some reason using the execute_process in ctest doesn't
like the "-D" options. Maybe I did something wrong? Here's what worked:
CopyToArchive.cmake.in:
include(CPackConfig.cmake)
EXECUTE
Eric,
I'm trying your idea and I feel like I'm so close to a solution. Here's the
call:
EXECUTE_PROCESS(
WORKING_DIRECTORY "${CTEST_BINARY_DIRECTORY}"
COMMAND ${CTEST_CMAKE_COMMAND}
-DCTEST_BINARY_DIRECTORY:STRING="${CTEST_BINARY_DIRECTORY}"
-DCTEST_CMAKE_COMMAND:STRIN
2009/10/14 Dixon, Shane :
> Clinton,
>
> Okay, that PARTIALLY works. It does in fact build everything the way it
> should. The problem comes when I try to copy the file. I don't know what
> the product of the Cpack step is unless I have visibility to the variable
> CPACK_PACKAGE_FILE_NAME. I
Hi,
I've run into a weird problem (using CMake 2.8 rc3). I want to use a
python script as a test-runner, and CTest crashes as a result. If I run
with -VV -debug, I can see this output before it crashes. If I run
exactly the same command line from the command prompt, everything works
as expected.
On Wed, Oct 14, 2009 at 11:31 AM, Clinton Stimpson wrote:
>
> I've found there's an xcode setting for this, but CMake doesn't put it in
> the
> generated xcode project.
> There's already a thing in the bug tracker for this.
> That would be ideal, instead of a method that requires root access and
>
On Wed, Oct 14, 2009 at 12:02 PM, Hendrik Sattler
wrote:
> Am Mittwoch 14 Oktober 2009 17:58:07 schrieb James Bigler:
>> Yes. What you need to do is add the DocBook/XML files to the
>> dependency list of the add_custom_command that is used to generate the
>> output file. When those files change,
I build the packages in a directory cleaned with each run, and use file(GLOB
...), to get the names of the packages. Then ssh to copy them to other
locations.
Clint
On Wednesday 14 October 2009 12:06:17 pm Dixon, Shane wrote:
> I tried this:
>
> LOAD_CACHE( ${CTEST_BINARY_DIRECTORY/CMakeCache
I tried this:
LOAD_CACHE( ${CTEST_BINARY_DIRECTORY/CMakeCache.txt
READ_WITH_PREFIX LOCAL_
CPACK_PACKAGE_FILE_NAME )
EXECUTE_PROCESS(
WORKING_DIRECTORY "${CTEST_BINARY_DIRECTORY}"
COMMAND ${CTEST_CMAKE_COMMAND}
-E copy ${LOCAL_CPACK_PACKAGE_FILE_NAME}.e
Am Mittwoch 14 Oktober 2009 17:58:07 schrieb James Bigler:
> Yes. What you need to do is add the DocBook/XML files to the
> dependency list of the add_custom_command that is used to generate the
> output file. When those files change, then the add_custom_command
> will be run again. See the docu
I'm running Cmake 2.8.0-rc3. Running "cmake --system-information" doesn't dump
anything, but tries to build in the current directory. This seems like a bug.
If anyone else can confirm this, I'll open a bug report for it.
--
Shane Dixon
Linux Engineer
Atmel Corporation
__
On Wednesday 14 October 2009 11:45:52 am Clinton Stimpson wrote:
> http://public.kitware.com/Bug/view.php?id=9125
> And there is a patch with it. There is a comment & link to the wiki saying
> to do it a different way, but the wiki didn't help any, as it tells me to
> do it the way I originally tr
Clinton,
Okay, that PARTIALLY works. It does in fact build everything the way it
should. The problem comes when I try to copy the file. I don't know what the
product of the Cpack step is unless I have visibility to the variable
CPACK_PACKAGE_FILE_NAME. I try this block:
EXECUTE_PROCESS(
http://public.kitware.com/Bug/view.php?id=9125
And there is a patch with it. There is a comment & link to the wiki saying to
do it a different way, but the wiki didn't help any, as it tells me to do it
the way I originally tried, but it didn't work.
But the code in question did compile and run
What's the issue number?
Is there a patch attached to it...?
On Wed, Oct 14, 2009 at 12:31 PM, Clinton Stimpson wrote:
>
> I've found there's an xcode setting for this, but CMake doesn't put it in
> the
> generated xcode project.
> There's already a thing in the bug tracker for this.
> That woul
I've found there's an xcode setting for this, but CMake doesn't put it in the
generated xcode project.
There's already a thing in the bug tracker for this.
That would be ideal, instead of a method that requires root access and changes
every xcode session.
Thanks,
Clint
On Wednesday 14 October
On Wed, Oct 14, 2009 at 04:59:17PM +0200, Theodore Papadopoulo wrote:
> We have a project which can be built either with static or dynamic
> libraries. The toggle
> is defined via an option named BUILD_SHARED which has some default value
> (let's say static).
>
> Unfortunately, after the first "
On Tue, Oct 13, 2009 at 4:16 PM, Hendrik Sattler
wrote:
> Hi,
>
> when changing a CMakeLists.txt file and calling make, then cmake automatically
> runs. I want to achieve the same thing but for specific files.
>
> The situation: DocBook/XML files are parsed at cmake times to get the names of
> the
Zitat von John Drescher :
I want to add doxygen support to my projects but my google searches
are not finding good recent information on how to do this. Or has
nothing changed in the last 3 years?
Create a normal configuration file for doxygen replace some of it by
variables and use configur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John Drescher wrote:
> I want to add doxygen support to my projects but my google
searches
> are not finding good recent information on how to do this. Or
has
> nothing changed in the last 3 years?
>
I have Doxygen files that I use. Features:
-
I have a situation where I have a few TPLs that are built via auto
tools and another project with CMake.
tpl1 -> lib1
tpl2 -> lib2
myproject -> libmyproj
I would like to combine the two TPLs into my project library. From
looking at previous postings on this list, it s
I want to add doxygen support to my projects but my google searches
are not finding good recent information on how to do this. Or has
nothing changed in the last 3 years?
--
John M. Drescher
___
Powered by www.kitware.com
Visit other Kitware open-sourc
We have a project which can be built either with static or dynamic
libraries. The toggle
is defined via an option named BUILD_SHARED which has some default value
(let's say static).
Unfortunately, after the first "configure" in ccmake all the libraries
are set to their values corresponding
to
@Eric:
Yes I agree with you. As you said, we all run out of time and the idea to
have a student doing that would be nice. Please keep us updated on this
matter.
I have come across this Eclipse plugin: http://www.cmakebuilder.com/ (I have
not tried but I guess the issue would be the same regarding
Also note that there _is_ CMake Editor support through a third party
plugin: http://cmakeed.sourceforge.net
The Eclipse Update site is:
http://cmakeed.sourceforge.net/eclipse/
The CMakeEd plugin provides syntax coloring, cmake command completion
and CMake Help for Eclipse. Note that the plu
24 matches
Mail list logo
