At 2/21/2006 02:59 PM, William A. Hoffman wrote:
API's and libraries are much harder to write than applications. So, you
may be on your own, as
we (Kitware) most likely do not have the time to maintain an API/library
for ctest.
Fair enough. We'll see what happens on our end.
You could still have
your programs call ctest with command line arguments, and your users would
not even need to know
it was there. I am sure your software uses some sort of installer, and
could make sure ctest was
installed in such a way as to not be noticed by your users.
That is an option. We consider such things for the vast array of things
that we embed in our software (including databases, encryption,
compression, XML decoding, and other things), and we have always preferred
library "embeddability" thus far.
We also have a set of our own libraries that are shared between all of our
applications, and we are comfortable with this library-creation process and
can do it pretty quickly. If we end up going this route (and it's way too
early to tell right now), we'll make our own internal library to interface
with Dart to share amongst our apps. If it makes sense to do so, we'll try
sharing this module with the outside world. (We plan on open-sourcing our
project, anyway, so everyone can view most of it, save for stuff we hold
back for commercial purposes...but that's a longer story outside the scope
of this thread.)
ctest as an executable can run without
CMake, and only requires a single executable.
That's good to know, and quite helpful. Can it be made with no dynamic
library dependencies outside of standard-system ones?
-Matt
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
