[CMake] ctest meant to be re-entrant?

[Chris Hillery]

On Mon, Jun 21, 2010 at 4:47 PM, Convey, Christian J CIV NUWC NWPT <
christian.convey at navy.mil> wrote:

> > David is right; it's confusing because ctest can be used in
> > several different ways. I think it's actually much worse than
> > he says, because as far as I can tell, ctest can be used in
> > four completely different and mutually incompatible ways,
> > each with their own idiosyncrasies. To make things worse, two
> > of the ways are actually invoked with the same arguments!
>
> Thanks, actually I'm really glad you wrote all that [snipped] stuff.  I was
> starting to think I was being uniquely moronic for having trouble figuring
> out ctest.  You confirmed that it really is pretty complicated in its
> current incarnation.  My self-respect is now partially restored.
>
> - Christian
>

Nope, you're not unique. :) CTest, and CMake too, do a lot of really neat
things and they do a lot of them really well. At the same time, it's
extremely clear that many of their facilities accreted over time as they
were needed, not with any overarching design goal in mind. The barrier to
entry for newcovers thus unfortunately grows ever taller.

But, back to the original subject, if you can re-state what your goal is a
little bit, hopefully we can figure out a way to get you there.

Ceej
aka Chris Hillery
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100621/a10df3d4/attachment.htm>