On Wed, Feb 09, 2011 at 05:24:28PM +0100, Verweij, Arjen wrote:
> Currently there is a python script that does preprocessing of all
> source, stores information in override.cmake files using
> set_source_file_properties(). This works fine, but makes maintaining
> source more error prone than it was
On Tue, Feb 08, 2011 at 04:56:26AM -0500, Martin O'Brien wrote:
> I definitely can't rely on the people who are complaining about having to do
> the -D... to have the correct version installed, or even to recognize when
> they don't, probably, and if I give them this option, they're going to write
(removing cmake-developers; cross-posting felt wrong)
On Thu, Feb 03, 2011 at 05:34:45PM -0500, David Cole wrote:
> Since we do not have a status of "backlog" -- but we don't really use the
> status values of "acknowledged" or "confirmed" very much, I am thinking we
> could define "backlog" as:
>
On Mon, Jan 31, 2011 at 08:12:49AM +0100, ycollette.nos...@free.fr wrote:
> if (MKL_FOUND)
> set(LINK_PATHS ${LINK_PATHS} "${mkl_solver_PATH}")
> endif (MKL_FOUND)
> if (MPI_FOUND)
> set(LINK_PATHS ${LINK_PATHS} "${MPI_BASE_PATH}/lib")
> endif (MPI_FOUND)
>
> link_directories(${LINK_PATHS})
D
On Fri, Jan 28, 2011 at 06:22:37AM -0500, David Cole wrote:
> Storing credentials on the machine in advance is one way to achieve this.
>
> (I have not tried this myself, but...) You may also be able to set the
> CTEST_UPDATE_COMMAND to a script that delegates to svn with all your desired
> comman
I have a CTest script that I use to drive dashboard builds. CTest
scripts return 0 (success) if everything works right, or non-zero
(failure; I'm getting 255 in this particular case on Linux) if something
goes wrong.
The problem I'm having is that I call ctest_test() in this script and I
have one
On Thu, Jan 27, 2011 at 08:40:14AM -0800, Tyler Roscoe wrote:
> On Thu, Jan 27, 2011 at 04:11:35AM -0800, girish hilage wrote:
> > find_program(CTEST_SVN_COMMAND NAMES svn)
> > set(CTEST_UPDATE_COMMAND "${CTEST_SVN_COMMAND}")
> > set(CTEST_UPDATE_
On Thu, Jan 27, 2011 at 04:11:35AM -0800, girish hilage wrote:
> find_program(CTEST_SVN_COMMAND NAMES svn)
> set(CTEST_UPDATE_COMMAND "${CTEST_SVN_COMMAND}")
> set(CTEST_UPDATE_OPTIONS "--username --password
> ")
>
> ctest_update(RETURN_VALUE updateRV)
>
> But, when I give 'ctest
On Wed, Jan 26, 2011 at 11:24:48AM -0600, kent williams wrote:
> cmake_minimum_required(VERSION 2.8)
> project(testo)
>
> function(set_a_var var value)
> set(${var} ${value})
> message("${var} = ${${var}}")
> endfunction()
>
> set_a_var(testo "HELLO!")
>
> message("outside func testo=${testo
On Thu, Jan 20, 2011 at 08:38:41PM +, Marco Craveiro wrote:
> the bit i fail to understand is why is 36000 deemed as a good value
> rather than ~86400? or is this because a lot of people have copied and
> pasted from the wiki page? :-)
Since the examples come from scripts Kitware uses in produ
On Thu, Jan 20, 2011 at 02:06:33PM +0100, Michael Wild wrote:
> Ah, yes. I keep forgetting. Might I propose that the documentation about
> regular expressions be extracted into its own section and then be
> referenced from all commands that have a REGEX mode? Because,
> confusingly, the only docume
On Mon, Jan 17, 2011 at 06:24:58PM +, mark...@email.it wrote:
>ln -s lib/libfreenect.so.0.0 lib/libfreenect.so
For this specific problem, check out:
http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:SOVERSION
> Should I use: add_custom_command ?
For the general problem of
On Fri, Jan 07, 2011 at 12:52:58PM +0100, ycollette.nos...@free.fr wrote:
> A while ago, a question similar to this one was posted, but no answer
> was given.
Link?
> Is it possible to perform the packaging part of a project only if the
> testing part has been successfully performed ?
I do this
On Mon, Jan 03, 2011 at 05:48:13AM -0800, girish hilage wrote:
> So, now I have to edit Test.xml generated by 'ctest' under directory :
> /home/girish/project/trunk/Testing/20110103-1027/
>
> What I would like to know is, if there is any 'CTEST_' variable which
> would give me path of t
On Mon, Dec 27, 2010 at 03:56:20PM +0100, Wojciech Migda wrote:
> I'm trying to pass information from a script executed for dashboard
> submission (ctest -S) to the underlying CMakeLists.txt which is to be
> parsed by (internally called by ctest) cmake. In other words, I'd like
> to have a system w
On Fri, Dec 24, 2010 at 04:19:16AM +, luxInteg wrote:
> in an execute_process() function with ${ECHO} (/bin/echo)what does one
> set for WORKING_DIRECTORY?
1. I would use ${CMAKE_COMMAND} -E echo rather than /bin/echo.
2. I would not set WORKING_DIRECTORY unless I needed it for some rea
On Tue, Dec 21, 2010 at 07:11:36PM +0100, Crni Gorac wrote:
> Am trying to employ fixup_bundle(), in order to be able to create
> installers for my Qt-dependent application on Mac and Windows. I have
> it working fine under Mac, but on Windows it is not working either
> with my application, or by
On Tue, Dec 21, 2010 at 10:04:25AM -0700, Aaron R> wrote:
> I'm trying to setup a cmake project on windows which needs the HDF5
> library. I put the prebuilt libraries under c:\hdf5-1.8.5-win32. I set
> HDF5_ROOT in the cmakelists file and then called find(HDF5). Its not
> finding it. I've trie
On Fri, Dec 17, 2010 at 10:40:30AM -0600, kent williams wrote:
> install(FILES ${CMAKE_BINARY_DIR}/FFTW/lib/libfftw3.a
> DESTINATION ${CMAKE_INSTALL_PREFIX}/lib)
> install(FILES ${CMAKE_BINARY_DIR}/FFTW/include/fftw3.h
> DESTINATION ${CMAKE_INSTALL_PREFIX}/include)
>
> I'm thinking thats kind of a
On Fri, Dec 10, 2010 at 08:11:45PM +0100, Louis Hoefler wrote:
> -- Build files have been written to: /root/massmailer/Debug
Probably not a good idea to be doing this kind of thing as root.
> [100%] Built target massmailer
> -- Configuring done
> -- Generating done
> -- Build files have been writ
On Thu, Dec 09, 2010 at 04:09:49PM -0500, David Cole wrote:
> No: we were ready to start collecting candidate bugs a month and a
> half ago. That list is now what you see on the roadmap page:
> http://public.kitware.com/Bug/roadmap_page.php
Guess I got my wires crossed.
I still believe the bug I
So are you ready to start collecting candidate bugs for 2.8.4? I
nominate this one!
http://www.vtk.org/Bug/view.php?id=11561
Thanks,
tyler
On Thu, Dec 09, 2010 at 03:37:16PM -0500, David Cole wrote:
> We are still planning to start the release candidate cycle for CMake
> 2.8.4 on Wed. Jan. 12, 2
On Thu, Dec 09, 2010 at 03:12:46PM -0500, John Drescher wrote:
> > I find it to work very well. What trouble are you having with it? I have
> > never had a problem with it, and it does save time.
> >
> Bill,
> Sorry, I take that back, I just checked and I no longer have it
> disabled in either o
On Thu, Dec 09, 2010 at 08:44:15AM -0500, Bill Hoffman wrote:
> On 12/9/2010 5:26 AM, Gabriel Petrovay wrote:
>> Thanks Bill for the trick.
>>
>> Unfortunately this works only for exe targets.
>> It doesn't work for dll's. Moreover, before the link command there is
>> this output: "Visual Studio No
ec 07, 2010 at 09:37:09PM -0800, Tyler Roscoe wrote:
> In the process of attempting to fix this, I learned a lot of stuff about
> how COST is handled that I've never encountered in the docs. Am I
> missing something?
>
> Here are some notes I made about the behavior of COST in CTe
test should run second in a fresh
# binary directory. Otherwise, since it failed previously, it should run first.
add_test (i_should_fail_and_run_second_or_first ${CMAKE_COMMAND} -E echo i
should fail and run second)
set_tests_properties (i_should_fail_and_run_second_or_first PROPERTI
On Tue, Dec 07, 2010 at 02:39:18AM -0600, j s wrote:
> Is there a way to pass the ctest -E flag to a visual studio 10 configuration
> to prevent certain tests from running in the regressions?
I don't know of a good way (and I'm not 100% sure what you mean by
"prevent certain tests from running in
the problem at its source would
obviously be preferable for me.
Thanks,
tyler
On Tue, Nov 30, 2010 at 12:14:56PM -0800, Tyler Roscoe wrote:
> On Tue, Nov 30, 2010 at 01:29:37PM -0500, Zach Mullen wrote:
> > Hm, yours was a use case we didn't really consider when we were making
tly
build that fixes this bug/regression/misunderstanding.
Thanks,
tyler
> On Tue, Nov 30, 2010 at 12:43 PM, Tyler Roscoe wrote:
>
> > On Fri, Nov 26, 2010 at 10:38:44AM -0500, Zach Mullen wrote:
> > > I just realized why this isn't working -- it's actually not a reg
On Thu, Nov 25, 2010 at 02:01:31PM +0100, Marcel Loose wrote:
> >>> On 24-11-2010 at 17:45, in message
> <20101124164507.gg23...@cryptio.net>, Tyler
> Roscoe wrote:
> > On Wed, Nov 24, 2010 at 12:11:56PM +0100, Micha Renner wrote:
> >>
> >> &g
On Fri, Nov 26, 2010 at 10:38:44AM -0500, Zach Mullen wrote:
> I just realized why this isn't working -- it's actually not a regression.
Maybe we have different definitions of "regression". I see a feature
that used to do one thing but which now does something else.
Here is what the docs say abou
On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
> On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer wrote:
> > So I think it is _really_ necessary to go through all the CMake
> > documentation items and add a line about when which feature was added.
> Adding that information in the docu
On Wed, Nov 24, 2010 at 12:11:56PM +0100, Micha Renner wrote:
>
> > SET(CMAKE_INSTALL_PREFIX "/foo/bar" CACHE PATH "Foo install prefix")
> >
> > So, without the test to CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT,
> > and without the FORCE option.
>
> No, as I mentioned, there was an article of
I use set_tests_properties (... COST -500) to force my code coverage
checks to run after all the unit tests have run. This has stopped
working and I'm reasonably confident that the only thing that changed
was an upgrade from cmake 2.8.0 or 2.8.1 to 2.8.3.
I couldn't find anything in the bug tracke
On Thu, Nov 18, 2010 at 10:55:15PM -0500, Braden Walters wrote:
> #Install headers
> set(HEADERS
> test.hpp)
> foreach(HEADER ${HEADERS})
> install(TARGETS ${CMAKE_CURRENT_SOURCE_DIR}/include/${HEADER}
> DESTINATION ${CMAKE_INSTALL_PREFIX}/include/PROJECT/${HEADER})
> endforeach()
Try
On Tue, Nov 16, 2010 at 10:15:28PM -0500, David Doria wrote:
> Is the goal simply to copy
> ...VTK/bin/libvtkHybrid.a
> into the package?
>
> I tried this:
> INSTALL(CODE "\${VTK_DIR}/bin/libvtkHybrid.a")
More like:
INSTALL(FILES "${VTK_DIR}/bin/libvtkHybrid.a")
tyler
___
On Thu, Oct 28, 2010 at 12:49:16PM -0500, Yaakov (Cygwin/X) wrote:
> We see the defining of WIN32 on Cygwin as a *bug*, not a feature, and it
> needs to be fixed outright.
I think the crux of the dilemma is this: what do you say to the people
who rely on this "buggy" behavior for their packages
On Mon, Oct 25, 2010 at 04:54:41PM +0200, Michael Wild wrote:
> On 25. Oct, 2010, at 16:45 , Marcel Loose wrote:
> > Wouldn't it make more sense to use 'make -k' instead?
>
> Some weeks ago I also wanted to propose this, but then realized one
> important drawback of -k: Say, you have target B dep
On Sun, Oct 24, 2010 at 04:35:45AM +0200, Michael Hertling wrote:
> On 10/24/2010 01:26 AM, Bill Spotz wrote:
> > #! ${PYTHON_EXECUTABLE}
Michael posted what I assume is a fantastic CMake solution :). Another
approach you might consider is to use:
#!/usr/vin/env python
which works out of t
On Tue, Oct 19, 2010 at 12:05:21PM -0700, J Decker wrote:
> WIthout adding a bunch of custom addtions, is there something I can
> test to see if a target is already defined?
Did you try 'if (TARGET ...)'?
tyler
___
Powered by www.kitware.com
Visit othe
On Mon, Sep 20, 2010 at 09:07:34AM -0700, Keith Gunderson wrote:
> I'm using a MSVC 9.0 Generator with Cmake 2.8.2
>
> How do I add a change so that the command for my RUN_TESTS project changes
> from
> the default of:
>
> "C:\Program Files\CMake 2.8\bin\ctest.exe" --force-new-ctest-process -C
On Mon, Sep 13, 2010 at 06:01:52PM +0200, Olivier Pierard wrote:
> - add_test( mpirun -machinefile $TMPDIR myexec ) => will never expand
> TMPDIR - I don't understand why because in CTestTestfile.cmake, I have
> add_test( test_name "mpirun" "-machinefile" "$TMPDIR" "myexec"); if I
> submit this as
On Sun, Aug 22, 2010 at 07:36:21PM +0100, Alexander Tarnopolsky wrote:
> I'm trying to invoke an interactive shell from a cmake script using the
> following:
>
> execute_process (COMMAND ${SHELL} ${ARGS})
>
> And the 32bit cmd.exe is invoked on "Windows 7 x64" (since the cmake
> itself runs in 3
On Wed, Aug 18, 2010 at 11:53:14AM +0200, Johny wrote:
> I am using a Ctest script to do a continuous build, however I can't seem
> to find a way to log the output of my make system since when you give
> ctest_build(BUILD src) it is automatically logged to the build.xml in
> the Testing direc
On Tue, Aug 17, 2010 at 05:14:07PM +0200, Johny wrote:
> I have a ctest script which i am using as a test in my build like this
>
> add_test ( ctest -S script.cmake)
>
> however once the script finishes executing i get a CMake error saying my
> CTEST_SOURCE_DIRECTORY, CTEST_BINARY_DIRECTORY and C
On Tue, Aug 17, 2010 at 03:35:02PM +0200, Lorenzo Natale wrote:
> Submit files (using http)
>Using HTTP submit method
>Drop site:[..]
> Error when uploading file: [...]/20100816-2200/Build.xml
>Error message was: Empty reply from server
I agree that CDash doesn't always produce the mos
On Thu, Aug 05, 2010 at 09:26:05PM -0500, Frank Gruman wrote:
> The problem - dependencies. Each build is supposed to be independent
> of any other. S:
>
> Build Project A-1
> Depends on B-1
> Depends on C-3
>
> Build Project A-2
> Depends on B-3
> Depends on C-3
>
>
On Thu, Jul 22, 2010 at 04:57:50PM +0200, Olaf van der Spek wrote:
> Why aren't empty dirs excluded by default?
Because if they were excluded, we would have someone on the list next
month asking why she can't create empty directories with install()
commands.
tyler
On Thu, Jul 15, 2010 at 03:39:20PM -0500, "Jörg F. Unger" wrote:
> I'm using cmake to add a test environment to our project (with ctest).
> Is there a possibility to generate to groups of test with different tags
> in the makefile, so that after the generation of the makefiles the user
> mig
On Fri, Jul 09, 2010 at 06:39:57PM +0200, Bo Thorsen wrote:
> Does this also work with binary files? From the documentation on FILE,
> this isn't really clear to me.
Why don't you try it and let us know?
tyler
___
Powered by www.kitware.com
Visit oth
On Wed, Jul 07, 2010 at 10:43:15PM -0400, John Drescher wrote:
> On Wed, Jul 7, 2010 at 9:44 PM, Clark Gaebel wrote:
> > I would like to generate file that looks something like this:
> >
> > // version.h
> > #define VERSION "v0.1-345-ga77ede8"
>
> You want to do that with configure_file
Th
On Mon, Jul 05, 2010 at 10:47:32AM -0400, John Drescher wrote:
> What is wrong with different build folders for each compiler / ide?
I'm interested in an answer to this question as well.
For me, the biggest thing is that it's what VS developers are accustomed
to. I've been educating it out of the
On Mon, Jul 05, 2010 at 01:31:41PM +0200, Mark Van Peteghem wrote:
> I see, thanks. I intend to write a Python script that adds the extra
> platform solution, because we really need that. Visual Studio and
> Code::Blocks project files are XML files, so it shouldn't be too hard.
If possible, I woul
On Thu, Jul 01, 2010 at 02:18:45PM -0500, Adarr, Lee wrote:
> After generating a Visual Studio 9 2008 Win64 solution, the solution
> contains only the x64 build specification. Is it possible to have CMake
Yes, this is as designed.
> add the win32 build specification to the same solution or must
Marcel,
Maybe I missed it earlier ITT, but I don't understand why you can't just
use if(FOO) instead?
tyler
On Thu, Jul 01, 2010 at 11:53:33AM +0200, Marcel Loose wrote:
> Hi Fraser,
>
> It doesn't. Well, partly it does, but unfortunately setting FOO to an
> empty string doesn't make it undefin
On Thu, Jun 24, 2010 at 03:07:50PM -0400, Convey, Christian J CIV NUWC NWPT
wrote:
> Suppose I want do just use "ctest" in a dead-simple manner: add a few
> lines to my CMakeLists.txt files, then run "cmake . && make test".
>
> In this scheme, what's the easiest way I can set CTEST_BUILD_NAME?
>
On Wed, Jun 23, 2010 at 03:58:59PM +0200, Aeschbacher, Fabrice wrote:
> Is there any way to split a custom command on multiple lines (for
> readability), e.g:
>
>ADD_CUSTOM_COMMAND(
> OUTPUT .patched
> COMMAND for patch in ${ARGV}; do\
> echo "applying $patch;
On Tue, Jun 22, 2010 at 08:30:43PM -0700, ben scott wrote:
> I know about the variable to add custom flags for g++, but how do I get rid
> if
> unwanted flags? I am writing a program for KDE on Linux and cmake insists on
Something like:
string(REPLACE "-ansi" "" CMAKE_CXX_FLAGS ${CMAKE_CXX_FL
On Fri, Jun 18, 2010 at 01:06:46PM -0400, David Cole wrote:
> On Fri, Jun 18, 2010 at 1:01 PM, Tyler Roscoe wrote:
> > On Fri, Jun 18, 2010 at 06:30:25PM +0200, Eric Noulard wrote:
> > > 2010/6/18 Tyler Roscoe :
> > > > 1. I want to change where "mak
On Fri, Jun 18, 2010 at 12:59:39PM -0400, Clark Gaebel wrote:
> What would I need to add to my CMakeLists.txt to make sure that a config
> file in the src/ directory gets copied to the build output directory,
> and the install directory when "make install" is run?
Have you looked at the install()
On Fri, Jun 18, 2010 at 06:30:25PM +0200, Eric Noulard wrote:
> 2010/6/18 Tyler Roscoe :
> > 1. I want to change where "make package" deposits the packages it
> > creates. Is there a way to do this -- some cpack variable I haven't
> > found?
>
> No
1. I want to change where "make package" deposits the packages it
creates. Is there a way to do this -- some cpack variable I haven't
found?
2. I want to get a hold of the name (or names) of generated packages. I
know the package will be called myproject.some_extension, but how do I
calculate "so
On Mon, Jun 14, 2010 at 01:40:38PM +0200, Aeschbacher, Fabrice wrote:
> > > I need to provide easy adding for source files to the developers,
> > > So it would be nice to just have a CMakelists.txt in every
> > subfolder,
> > > which then edits the source-variable.
> >
> > Also consider to use pr
I just looked at your email address and now I'm pretty sure I know why
I've had "Lonely Rolling Star" from the Katamri Damacy soundtrack stuck
in my head all morning :).
On Mon, Jun 07, 2010 at 02:14:00PM -0400, Nathan Huesken wrote:
> > 1. Why do you need to nest one project inside the other? I t
the debug and optimized flags for target_link_libraries().
tyler
> On Mon, Jun 7, 2010 at 2:50 PM, Tyler Roscoe wrote:
>
> > On Mon, Jun 07, 2010 at 02:43:35PM -0300, Felipe Sodré Silva wrote:
> > > I need to write a CMakeLists file to generate a VS 2005 project in which
On Mon, Jun 07, 2010 at 02:43:35PM -0300, Felipe Sodré Silva wrote:
> I need to write a CMakeLists file to generate a VS 2005 project in which I
> can have different project settings for Debug and Release configurations.
>
> For example, I need to have a set_target_properties directive for Release
On Mon, Jun 07, 2010 at 11:54:12AM -0400, Nathan Huesken wrote:
> I have a cmake project into which I want to nest another cmake project.
> The nested cmake project is a complete project working on its own, and
> the outer cmake project depends on it.
> So when the outer cmake project is build, the
On Thu, May 27, 2010 at 09:51:19PM +0200, Michael Hertling wrote:
> > add_library ( STATIC ${SOURCES} ${HEADERS} )
>
> In general, there's no need to specify headers in ADD_LIBRARY() or
> ADD_EXECUTABLE(). Usually, this does no harm, but dependencies of
> source files on headers are figured out
On Fri, May 21, 2010 at 02:04:38PM -0700, Torsten Rohlfing wrote:
> FIND_PACKAGE(ZLIB)
> IF(ZLIB_FOUND)
> MESSAGE( WARNING "HAVE system zlib" )
> ELSEIF(ZLIB_FOUND)
> MESSAGE( WARNING "NO system zlib" )
> ENDIF(ZLIB_FOUND)
I don't see an else clause here, just two ifs (that check the same
cond
On Tue, May 18, 2010 at 05:37:32PM +1000, ross hennessy wrote:
> ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/${CMAKE_CFG_INTDIR}, which as I'm on
> windows (I don't think this gets set on linux?), evaluates to either
> ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/Debug or
> ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/Release. So
On Mon, May 17, 2010 at 02:41:21PM -0400, Michaël Presseau wrote:
> Hi, I have an application and I need to create an installer. I use
> CPack with NSIS. For now, I'm using : find_package(Boost COMPONENTS
> thread date_time filesystem REQUIRED)
>
> This give me le .lib associate to the dll file. T
On Mon, May 17, 2010 at 12:53:34PM -0500, kent williams wrote:
> "Internally, CPack will use CMake's install mechanism to automatically
> populate the package."
Right. Mostly, all that CPack does is call "make install" on your
project with a special CMAKE_INSTALL_PREFIX.
> but when I add
>
> inc
You probably need the Prefix Hack:
http://www.itk.org/Bug/view.php?id=8243
tyler
On Mon, May 17, 2010 at 09:53:34AM -0500, aaron.mead...@thomsonreuters.com
wrote:
> Hi All!
>
>
>
> I'm trying to migrate an existing Visual Studio 8 2005 source tree to
> CMake. The only problem I'm having rig
On Sat, May 15, 2010 at 05:53:45PM +0200, Baptiste Lepilleur wrote:
> I initially tried using the variable ${CMAKE_BUILD_TYPE} but it seems to
> always expand to a blank string, and the doc imply that it does not work
> with Visual Studio solution as it has multiple configurations. So I switched
C
On Fri, May 14, 2010 at 01:41:22PM -0500, Kevin Burge wrote:
> I'd like to add a "setup" target that depends on "install" so I can just
> do "make setup".
>
> Does anyone have a work around while we wait on
> http://public.kitware.com/Bug/view.php?id=8438?
You could write a custom_target "my_i
On Fri, May 07, 2010 at 01:55:44PM -0700, Tyler Roscoe wrote:
> I have the following warning in my project build:
>
> /.../rs/sdk/trunk/internalheaders/minorrev/_build/util/svnutils.py:34:
> DeprecationWarning: os.popen4 is deprecated. Use the subprocess module.
>
> infile,
Let's keep this on the list in case it helps someone else.
On Fri, May 07, 2010 at 10:27:16PM +0100, Magnus Therning wrote:
> On 07/05/10 17:24, Tyler Roscoe wrote:
> > On Fri, May 07, 2010 at 04:41:23PM +0100, Magnus Therning wrote:
> >>>add_custom_comm
On Fri, May 07, 2010 at 05:10:59PM -0400, Bill Lorensen wrote:
> I get the subject message.
>
> I have defined
> set( CTEST_GIT_COMMAND "git" )
> SET(UPDATE_COMMAND "${GITCOMMAND}")
> SET(UPDATE_OPTIONS "${GIT_UPDATE_OPTIONS}")
Did you try CTEST_UPDATE_COMMAND and CTEST_UPDATE_OPTIONS?
Are you s
I just posted this to the CDash mailing list. Julien pointed out that
this is actually a CTest problem (since CTest writes the XML saying what
warnings happened during the build) and suggested I repost over here.
I have the following warning in my project build:
/.../rs/sdk/trunk/internalheaders/
On Fri, May 07, 2010 at 04:41:23PM +0100, Magnus Therning wrote:
> > add_custom_command (TARGET ${PROJECT_NAME}
> > POST_BUILD
> > # Call the runner script directly. By doing it this way, all the
> > # unit tests in the executable run at once. If we call CTes
On Fri, Apr 30, 2010 at 12:03:12PM -0400, Brad King wrote:
> Unfortunately this can't be fixed upstream without breaking the
> legacy extension-finding feature.
Isn't this what CMake policies are for? Or is the offending code buried
in some dark corner where policies won't help?
tyler
___
On Tue, Apr 27, 2010 at 02:47:18PM +0100, Magnus Therning wrote:
> Except of course that it will take away one of the things I *really*
> want, which is that all unit tests are run every time I compile.
We run our unit tests with a python wrapper script that does some
environment configuration bef
On Fri, Apr 23, 2010 at 04:24:06PM +0100, Magnus Therning wrote:
> A project that I'm currently trying to convert over to CMake has
> several unit tests written as standalone executables. Are there any
> examples around for integrating the running of such tests as part of
> the build in CMake?
ad
On Tue, Apr 13, 2010 at 12:39:13PM +0200, Yegor Yefremov wrote:
> With this expression
>
> set(CPACK_NSIS_CREATE_ICONS "CreateShortCut
> \$SMPROGRAMS\\$STARTMENU_FOLDER\\${PROJECT_NAME}.lnk
> \$INSTDIR\\${PROJECT_NAME}.exe")
>
> I can successfully create a package, but cmake/cpack shows a warni
On Mon, Apr 12, 2010 at 01:15:11PM -0400, Zou, Di (Cont, ARL/CISD) wrote:
> I replaced:
> ctest_configure(OPTIONS "-C ~/NetDMF_CMake_Config")
> with:
> ctest_configure(OPTIONS "-C $ENV{HOME}/NetDMF_CMake_Config")
>
> I get the same error:
> Configure Command:"/usr/cta/CSE/Release/cmake-2.8.0.5/bin
On Mon, Apr 12, 2010 at 12:11:54PM -0400, Zou, Di (Cont, ARL/CISD) wrote:
> I have this line in my ctest script:
> ctest_configure(OPTIONS "-C ~/NetDMF_CMake_Config")
>
> At the dashboard, this is the error I get:
> Build Name:build-linux-c++
>
> Configure Command:"/usr/cta/CSE/Release/cmake-2.8.
On Fri, Apr 09, 2010 at 08:53:27PM +0200, Alexander Neundorf wrote:
> > set (CPACK_INCLUDE_TOPLEVEL_DIRECTORY 0)
>
> Is this documented somewhere ?
> If not, can you please put it in the wiki (e.g. in
This finally motivated me to create an account for the kitware wiki.
Thanks Alex :).
I added a
On Fri, Apr 02, 2010 at 09:50:59PM +0200, Allan W. Nielsen wrote:
> The result of this the the following file:
> TEST-0.1.1-Linux/bin/test
>
> What I would like to achieve is that the directory layout of the
> generated tar file is:
>
> /bin/test
>
> or maby
>
> bin/test
Look at:
set (CPACK_I
On Fri, Mar 26, 2010 at 05:20:21PM -0500, Richard Wackerbarth wrote:
> Now that the setup scripting is more complex, I'm trying to use your
> "cmake_common.cmake" script for my CMake submissions. Tracking changes
> to that script would be much easier for me if you have it published in
> a publicly
On Wed, Mar 24, 2010 at 09:28:32AM -0300, Felipe Sodre dos Santos wrote:
> I wondered if something like that was happening.
> And how exactly does ctest does this?
It passes a timestamp to svn update. Check the Update logs under
${CMAKE_BINARY_DIRECTORY}/Testing (you might need the Temporary
dir
On Tue, Mar 23, 2010 at 04:50:54PM -0300, Felipe Sodre dos Santos wrote:
> Last night my nightly build broke, and after making some changes in
> the code and submitting to SVN server, it works for the experimental
> build. However, when I try the Nightly one again, it breaks exactly
> the same way
On Mon, Mar 22, 2010 at 05:47:15PM -0700, aaron_wri...@selinc.com wrote:
> So... no easy answer for this? The only reason I bring this up is that
> I've looked at the cmake version of boost, and it requires a library of
> several cmake files full of macros and functions that help get their
> pro
On Tue, Mar 23, 2010 at 02:43:45PM +0530, Kiran Gopal Patil wrote:
> I do have the CMakeLists.txt for the main and sub1,2,3 are added in it which
> inturn add sub11,22,33
>
> I want to do "make test" for full project at directory main.
> In addition to this I want to do "make test" for sub11,22,3
On Mon, Mar 22, 2010 at 06:40:21PM -0400, Simmons, Aaron wrote:
> if (CMAKE_BUILD_TYPE STREQUAL Debug)
> set_source_files_properties( myfile.cpp PROPERTIES COMPILE_FLAGS
> -DMYFLAG=asdf )
> endif (CMAKE_BUILD_TYPE STREQUAL Debug)
>
> However, for multi-configuration bu
Following up on this thread:
http://public.kitware.com/pipermail/cmake/2010-February/035197.html
It's not as elegant as I would like -- support for ctest_update(...
APPEND ...) would be much cleaner, but I didn't have the bandwidth to
take on that project at this time -- but I believe I have a hac
I have a lot of complaints about Installshield, but I'll spare you the
whinging and just say that I need to generate Installshield setups at
the end of our CMake build. I am considering some options and was
wondering if anyone else has experience with this.
Currently, our build process is driven b
On Sat, Mar 20, 2010 at 07:30:36PM +0100, Theodore Papadopoulo wrote:
> All the tests (in the test directory) that use the DLL in the src
> directory fail at runtime because they do not
> find the dll... I suspect this is because of a different directory. All
> the examples I have found use the s
On Mon, Mar 22, 2010 at 11:51:51AM -0400, David Cole wrote:
> Never use "rebuild all" with a cmake generated *.sln file... Just use "Build
> Solution"...
Interesting. David, can you elaborate?
tyler
___
Powered by www.kitware.com
Visit other Kitware op
On Fri, Mar 19, 2010 at 10:08:39AM -0300, Felipe Sodre dos Santos wrote:
> SET (CTEST_UPDATE_COMMAND "svn")
> SET (REPO_USERNAME nightly_builder)
> SET (REPO_PASSWORD nightly_builder_pass)
> SET (REPO https://myrepo/svn/myproject/trunk)
> SET (CTEST_CVS_CHECKOUT "svn co ${REPO} --username ${REPO_US
This page:
http://www.cmake.org/Wiki/CPack:Generator_Information
redirects to a page called:
VTK/Tutorials/PythonEnvironmentSetup
which AFAICT has nothing at all to do with CPack generators. The topics
are so different that I can't even guess what someone was trying to
accomplish by enacting this
1 - 100 of 504 matches
Mail list logo
