Is that 10 Total? I am submitting tests with the same site/name all
that, just updated results but the results don't seem to be "taking".
Hmm. 10 tests. I guess I'll have to be more conservative when I post a
test.
_
Mike Jackson
David Cole wrote:
In the script, prior to the ctest_build call, do:
set(CTEST_BUILD_FLAGS -j4)
(only works with make that supports -j, obviously...)
We often do this in our scripts:
set(CTEST_BUILD_COMMAND "make -j4 -i")
MAKECOMMAND:STRING=/usr/bin/make -i -j4
I don't think we will add the m
On 30. Nov, 2009, at 17:52 , Bill Hoffman wrote:
Michael Wild wrote:
That's not a real solution for me, since I intend to distribute my
source code and people won't be happy if their download fails. And
replacing the DLL/so/dylib isn't an option either, because this
requires too much man
Is it only the messages printed to the screen that you're concerned
with?
Michael
On 30. Nov, 2009, at 18:39 , Alexander Tarnopolsky wrote:
Thanks for prompt response!
The real reason for inclusion of those "external" sources is the
size of
our projects.
We have read-only "shared/publi
In the script, prior to the ctest_build call, do:
set(CTEST_BUILD_FLAGS -j4)
(only works with make that supports -j, obviously...)
On Mon, Nov 30, 2009 at 3:05 PM, Alexander Neundorf wrote:
> Hi,
>
> I'm running some dashboard builds and didn't find a way how to make the
> builds
> (via ctest_
Hi,
I'm running some dashboard builds and didn't find a way how to make the builds
(via ctest_build()) run parallel, e.g. make -4.
For ctest_test() there is a PARALLEL_LEVEL option, I didn't find this for
ctest_build().
Is it possible to do this ?
Alex
__
On Monday 30 November 2009, Romain CHANU wrote:
> Hi,
>
> Thank you for your answer.
>
> I want to compile on both Linux and Windows with the same CMakeLists.txt. I
> will have a look to the different variables.
Ok, so this is not cross compiling, you don't need any toolchain files or
anything el
On Friday 27 November 2009, Julien Michel wrote:
> Dear cmake users,
>
> I ma stuck with some dependencies problem and I can not figure out why
> my cmake project behave like that :
> make BaseDoxygen
> -> 100% built
> make BaseJar :
> -> make[2]: *** No rule to make target « BaseDoxygen » ...
> ma
On Sunday 29 November 2009, j s wrote:
> Hello,
>
> I am running:
> cmake version 2.4-patch 7
>
> on Ubuntu 8.04 and I can't get this option to work, whether it is in
> CMakeLists.txt or on the command line.
>
> rm CMakeCache.txt; cmake -DCMAKE_BUILD_WITH_INSTALL_RPATH=TRUE
> -DCMAKE_INSTALL_RPATH
On Tue, Nov 24, 2009 at 04:15:19PM -0600, Voisard, Shane S CIV NSWCDD, K54
wrote:
> set (CMAKE_CONFIGURATION_TYPES "Release" CACHE STRING "" FORCE)
>
> I tried this alternative, with no effect, based upon online 2.6 documentation:
>
> set (CMAKE_CONFIGURATION_TYPES "Release" CACHE INTERNAL "" FO
Thanks for prompt response!
The real reason for inclusion of those "external" sources is the size of
our projects.
We have read-only "shared/public" workarea were all the sources reside.
The developer checks-out only the files that should be modified during
his current task (his source files are
I was wanting to hack around a bit in the CMake code based in order to
add in a "feature" to have Build directories ignored by TimeMachine on
OS X 10.5 and above. Xcode seems to do this automatically for you but
if you use any of the other generators then you are out of luck. I
realize I _c
Michael Wild wrote:
That's not a real solution for me, since I intend to distribute my
source code and people won't be happy if their download fails. And
replacing the DLL/so/dylib isn't an option either, because this requires
too much manual intervention.
That means I'm probably stuck with
Apart from me not liking this setup (those external sources should
probably be a separate project and be compiled as a library which then
is imported) you could use
CONFIGURE_FILE(/long/path/to/file ${CMAKE_BINARY_DIR}/file COPYONLY)
and then pass ${CMAKE_BINARY_DIR}/file to the add_executabl
Dear CMake users list,
In our build system we have to compile source files that reside out of
source/build tree. In some cases there are several hundreds of such
"external" sources in a project.
Consider simplified CMakeLists.txt:
===
Project (system)
set(SOURCES
On 30. Nov, 2009, at 16:33 , Bill Hoffman wrote:
Michael Wild wrote:
Hi all
Are there any plans to enable SSL-support in the CMake-included
CURL library?
The CMake binaries will never ship with ssl (due to export control
issues). However, you can build CMake yourself and turn on the
b
Michael Wild wrote:
Hi all
Are there any plans to enable SSL-support in the CMake-included CURL
library?
The CMake binaries will never ship with ssl (due to export control
issues). However, you can build CMake yourself and turn on the build
option to use SSL with the CURL. I might be ab
On Monday 23 November 2009 10:38:27 Marcus D. Hanwell wrote:
> On Monday 23 November 2009 10:03:35 Mark Moll wrote:
> > Between cmake 2.6.4 and cmake 2.8 the following lines were removed from
> > the FIND_LIBRARY(PYTHON_LIBRARY ...) command in FindPythonLibs.cmake:
> >
> > -PATH_SUFFIXES
> > -
Bill Hoffman wrote:
> Bill Spotz wrote:
>>> when the epetra dynamic library gets linked under the new cmake and
>>> not the old. This could be problematic because it is using the
>>> compiler /usr/bin/c++, which on my system is version 4.0.1 (although
>>> the gfortran compiler is version 4.4.1).
>
Hi Russell,
Thanks for tracking this down to such a specific set of conditions.
If you hadn't done that work up front it might have taken a while to
find this.
Russell Yanofsky wrote:
> I think a safe and straightforward fix would be to make cmake use
> SystemTools::CollapseFullPath for the path
John,
I actually have this same problem with a ParaView plugin that I am
developing. I have the following in the plugin's CMakeLists.txt file
( where MXA_OUTPUT_DIRS_DEFINED _is_ defined in the before the
CMakeLists.txt is included via an 'add_subdirectory()' command from
the MXADataMode
I forwarded it along... We'll see if it works good and let you know.
On Mon, Nov 30, 2009 at 7:40 AM, David Doria wrote:
> > I wrote a cmake highlighting for geshi earlier this year, if you install
> the
> > geshi plugin for mediawiki, and place the attached file in your geshi
> folder,
> > you
> I wrote a cmake highlighting for geshi earlier this year, if you install the
> geshi plugin for mediawiki, and place the attached file in your geshi folder,
> you should be able to get highlighting like so:
>
> project(test)
>
>
> There are a few bugs, such as nested variables ${${foo}}, but it
Hi,
Thank you for your answer.
I want to compile on both Linux and Windows with the same CMakeLists.txt. I
will have a look to the different variables.
Cheers,
Romain
2009/11/30 Johannes Stallkamp
> Hello Romain,
>
> Romain CHANU schrieb:
> > If I need to compile a library on both Linux and
Hi all
Are there any plans to enable SSL-support in the CMake-included CURL
library?
Michael
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topi
I am in the process of switching the hdf5 library used by paraview from the
older 1.6.x to the newer 1.8.x and I encountered a problem caused by the fact
that the new variable
CMAKE_LIBRARY_OUTPUT_DIRECTORY
is set by hdf1.8.x when included in the paraview main project - and it
overrides the LIBR
Hi David,
Why not use OPTION(...) for this, or if you really want to the
equivalent: set(MYVAR ON CACHE BOOL "My variable"). Don't use FORCE, or
you will overwrite any changes the user made.
Best regards,
Marcel Loose.
On Sun, 2009-11-29 at 10:12 -0500, David Cole wrote:
> if(BUILD_PARAVIEW_PLUG
On Sunday 29 November 2009 11:14:03 am David Doria wrote:
> I was wondering if there was any talk of adding cmake script support
> to mediawiki's >source lang="X"> capability.
>
> It looks terrible if you just use "text":
> http://www.cmake.org/Wiki/Paraview_Make_building_Paraview_plugin_optional
Hello Romain,
Romain CHANU schrieb:
> If I need to compile a library on both Linux and Windows, the best
> CMake practice would be to write toolchain files for Linux and
> Windows (cf. http://www.cmake.org/Wiki/CMake_Cross_Compiling)
>
> Is that correct?
Do you really want to cross-compile (i.e. b
29 matches
Mail list logo