Going into the build configuration and telling it to run tests, (I think the
checkbox is RUNTESTS, but I don't have my laptop here), causes it to run
tests as it is trying to compile the main executable for my project.

The directory structure is:
lib1
lib2
lib3
main (location of the main() entry point of the program)
testing

CTEST is being called before it is done compiling my application.

Regards,

Juan

On Thu, Jul 30, 2009 at 1:38 PM, David Cole <david.c...@kitware.com> wrote:

> If something is non-deterministic then it means there is a missing
> dependency somewhere...
> This should work. We have many dashboards that run with parallel Visual
> Studio builds and work reliably day after day. Whenever I have seen a
> problem with it, there has always been a missing depedency expression in the
> CMakeLists.txt files.
>
> What exactly is it that does not build in the proper order? (Send along
> some CMakeLists snippets perhaps...)
>
> When you say "RUNTESTS (I can't remember) enabled" that does not really
> help us help you. If you could just post the error output, perhaps the group
> can spot something...
>
>
> David
>
>
> On Thu, Jul 30, 2009 at 2:16 PM, j s <j.s4...@gmail.com> wrote:
>
>> I guess I won't be using the parallel option in Visual Studio, then.  A
>> non-deterministic build order is not worth the risk.
>>
>> Juan
>>
>>
>> On Thu, Jul 30, 2009 at 10:53 AM, John Drescher <dresche...@gmail.com>wrote:
>>
>>> On Thu, Jul 30, 2009 at 11:44 AM, j s<j.s4...@gmail.com> wrote:
>>> > By default visual studio uses 2 threads on my machine, a dual core AMD.
>>> >
>>> > I notice when I have RUNTESTS (I can't remember) enabled, it may
>>> attempt to
>>> > run the tests before my project is even built.
>>> >
>>> > If certain sub directories depend on a target in another directory
>>> already
>>> > being built, is it safe to use the multi-threaded option in visual
>>> studio?
>>> >
>>>
>>> I have been using parallel builds with visual studio 2005 for over 1
>>> year. It sometimes creates situations like this but since it saves me
>>> 10s of minutes per day I deal with the issues. Generally building the
>>> same project a second time fixes any problems and is usually quick
>>> since most stuff builds correctly on the first pas.
>>>
>>> John
>>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the CMake FAQ at:
>> http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake
>>
>
>
_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to