On Mar 31, 2011, at 4:43 PM, Nicolas Desprès wrote:
On Fri, Apr 1, 2011 at 12:22 AM, Belcourt, Kenneth
wrote:
This is probably old news but is there some reason why I can build
my code
in parallel with make -j8, for example, but trying to run the tests
in
parallel with make -j8 tests ign
On Fri, Apr 1, 2011 at 12:22 AM, Belcourt, Kenneth wrote:
> Hi,
Hello,
>
> This is probably old news but is there some reason why I can build my code
> in parallel with make -j8, for example, but trying to run the tests in
> parallel with make -j8 tests ignores the -j option. I've resorted to
>
Hi,
This is probably old news but is there some reason why I can build my
code in parallel with make -j8, for example, but trying to run the
tests in parallel with make -j8 tests ignores the -j option. I've
resorted to invoking ctest with -j8 which works fine. Any way to
normalize the b
On 2/28/2011 10:07 AM, Michael Wild wrote:
On 02/28/2011 03:57 PM, Chris Green wrote:
On 2/28/11 8:13 AM, Michael Wild wrote:
On 02/28/2011 03:03 PM, Chris Green wrote:
Try this:
make test ARGS=-j12
Bingo!
Thank you,
Chris.
Just a warning: AFAIK this is undocumented and I found it out
On 02/28/2011 03:57 PM, Chris Green wrote:
> On 2/28/11 8:13 AM, Michael Wild wrote:
>> On 02/28/2011 03:03 PM, Chris Green wrote:
>
>>> Try this:
>>>
>>> make test ARGS=-j12
> Bingo!
>
> Thank you,
>
> Chris.
>
Just a warning: AFAIK this is undocumented and I found it out by looking
at the Ma
On 2/28/11 8:13 AM, Michael Wild wrote:
> On 02/28/2011 03:03 PM, Chris Green wrote:
>> Try this:
>>
>> make test ARGS=-j12
Bingo!
Thank you,
Chris.
--
Chris Green , FNAL CD/ADSS/CET; 'phone (630) 840-2167.
IRC: gre...@jabber.fnal.gov, chrisgr...@jabber.dsd.lbl.gov;
chissgreen (AIM, Yahoo); ch
On 02/28/2011 03:03 PM, Chris Green wrote:
> Hi,
>
> I would have expected this naively to be a FAQ already, but the almighty
> Ge wasn't particularly helpful. If I *have* missed the answer
> somehow, please accept my apologies and I'd appreciate a brief pointer
> to the right place to find it
Hi,
I would have expected this naively to be a FAQ already, but the almighty
Ge wasn't particularly helpful. If I *have* missed the answer
somehow, please accept my apologies and I'd appreciate a brief pointer
to the right place to find it:
I'm investigating upgrading our build system from CM
- renaming didn't solve it
Instead I moved ENABLE_TESTING() from test/CMakeListst.txt to my root
CMakeLists.txt
I think this is not stated in the documentation.
Thanks everybody!
jochen
>
> It is possible your example above is not complicated
> enough to trigger the clash.
to trigger the clash. For example, your test
> subdirectories are just created, but you do not have an
> add_subdirectory(test) command to actually run cmake within that
> test subdirectory.
>
> So I would suggest to the OP that they do rename their test directory
> to something
uld suggest to the OP that they do rename their test directory
to something else because I am pretty sure that will solve the issue.
Until PLplot did that (for a much earlier version of CMake) "make
test" failed to work for us.
Alan
Maybe, you could post your CMakeLists.txt for fur
On 11/08/2010 10:03 PM, Jochen Issing wrote:
> Hi list,
>
> I tried to add ctest to my project and did this by adding ENABLE_TESTING()
> and several ADD_TEST(...) to my CMakeLists.txt file.
> The tests are run on executables, which are built inside a dedicated test
> directory in my project root
Hi list,
I tried to add ctest to my project and did this by adding ENABLE_TESTING() and
several ADD_TEST(...) to my CMakeLists.txt file.
The tests are run on executables, which are built inside a dedicated test
directory in my project root and the execs show up in my Makefile.
After reading thro
Are you looking for something like this...?
if(TARGET foo)
add_test(footest foo)
endif()
On Wed, Oct 21, 2009 at 2:33 PM, Theodore Papadopoulo <
theodore.papadopo...@sophia.inria.fr> wrote:
> From the documentation of add_dependencies:
>
> Make a top-level target depend on other top-level tar
From the documentation of add_dependencies:
Make a top-level target depend on other top-level targets. A top-level
target is one created by ADD_EXECUTABLE, ADD_LIBRARY, or ADD_CUSTOM_TARGET.
A test is thus not a valid target to add dependencies to.
Often, one wants to build an executable only
On 2008-03-28 22:31+0100 Alexander Neundorf wrote:
I think simply having test depend on all may be a bit slow.
I agree that is a concern for bigger projects like paraview with half-minute
"make all" latency (as recently demonstrated by Bill) so it appears our goal
should be to have a DEPENDS o
On Friday 28 March 2008, Alan W. Irwin wrote:
> On 2008-03-28 20:59+0100 Alexander Neundorf wrote:
...
> > Then it's also more obvious that it doesn't depend on all
>
> I am probably missing something because I don't understand this comment.
I meant: if somebody runs a tool different from make, he
On 2008-03-28 20:59+0100 Alexander Neundorf wrote:
On Friday 28 March 2008, Alan W. Irwin wrote:
On 2008-03-14 13:04-0700 Alan W. Irwin wrote:
Another concern with the current "make test" is it does not depend on the
default "all" target. That is a bad oversight IMO, since the current
situati
On Friday 28 March 2008, Alan W. Irwin wrote:
> On 2008-03-14 13:04-0700 Alan W. Irwin wrote:
> > Another concern with the current "make test" is it does not depend on the
> > default "all" target. That is a bad oversight IMO, since the current
> > situation is you will be running out-of-date test
On 2008-03-14 13:04-0700 Alan W. Irwin wrote:
Another concern with the current "make test" is it does not depend on the
default "all" target. That is a bad oversight IMO, since the current
situation is you will be running out-of-date tests after some code fixup
unless you remember to run "make"
On Friday 14 March 2008, Alan W. Irwin wrote:
> On 2008-03-13 21:18-0400 David Cole wrote:
> > For it to work, there has to be an "ENABLE_TESTING()" in the top level
> > CMakeLists.txt file. And at least one ADD_TEST somewhere in the tree...
> > "make test" should be equivalent to running "ctest" i
On 2008-03-13 21:18-0400 David Cole wrote:
For it to work, there has to be an "ENABLE_TESTING()" in the top level
CMakeLists.txt file. And at least one ADD_TEST somewhere in the tree...
"make test" should be equivalent to running "ctest" in the top level binary
directory. (Or any sub-directory f
[EMAIL PROTECTED] wrote:
Hi all!
I'm trying to integrate cppunit tests using cmake in our ims library and
cannot solve the problem how to build tests executables only by demand,
i.e. by calling 'make test'. I'm quite new to cmake and don't know if this
is possible at all, but I suppose it should
Hi all!
I'm trying to integrate cppunit tests using cmake in our ims library and
cannot solve the problem how to build tests executables only by demand,
i.e. by calling 'make test'. I'm quite new to cmake and don't know if this
is possible at all, but I suppose it should be possible :-)
I have fou
I got the following failures on x86/Solaris trying to build cmake 2.4.6.
Here is the output:
6/14 Testing: kwsys.testProcess-4
6/14 Test: kwsys.testProcess-4
Command: "/home/install/gnu/src/cmake-2.4.6/Tests/kwsys/testProcess" "4"
Directory: /home/install/gnu/src/cmake-2.4.6/Tests/kwsys
"kwsys.t
On Wed, 2006-08-23 at 11:12 -0400, Brad King wrote:
> Your "make" program is finding the "test" directory on disk and assumes
> the target is up to date. Don't call the directory "test".
Thanks Brad! That did it.
Best,
Scott
___
CMake mailing list
CMa
Scott Amort wrote:
> I have come across some strange behaviour with testing and my CMake
> files. My project is structured like this:
>
> main project
> -- src
> -- test
> -- subproject1
> src
> test
[snip]
> The idea is that the main project builds all the subprojects first, then
> its
Hi All,
I have come across some strange behaviour with testing and my CMake
files. My project is structured like this:
main project
-- src
-- test
-- subproject1
src
test
-- subproject2
src
test
-- subproject3
src
test
...etc.
The idea is that the main project bui
28 matches
Mail list logo
