Re: [Cppunit-devel] Patch for VC++ testrunner...

[Bastiaan B. <bas...@li...>]

Baptiste Lepilleur wrote:

> > The borland port seems not to use MFC, indeed. But it looks like the
> msvc++ and
> > borland versions share large parts of the code.  Better to have that part
> in
> > the tree only once, and abstract the GUI interface.
> > So I still prefer a win32 subdir over an msvc one: when someone wants to
> > support borland, s/he can start from there and split out the concrete GUI
> > calls.
>     I gave it a quick look, and the closest common stuff I could find was
> the GUITestResult class, yet even the synchronization mecanism was removed
> (it look like the Borland version does not run the test in a separate
> thread). Not worth factoring out, since it would make it hard to change a
> project without impacting the other, therefore reducing the velocity of
> change.
>     The test runner itself is pretty simple : 1 class for the dialog, 1
> class that prograte result to the dialog, 1 class for the ActiveTest
> (threaded test), and a few other support class that don't to much. Each of
> this is compiler specific....
>

OK, I just briefly glanced over it and saw that both had a lot of filenames in
common, which hinted at a similar structure  at least. Apparently it's not that
simple :-(
I'll let the portability issue rest until someone actually wants to spend
effort into supporting borland or other compilers.


>
> > OK, it does not work. But I've found another way, which is more
> convenient:
> > With the 'dist-hook' target one can specify commands to run after the dist
> dir
> > has been created, but before it has been tarred. Here we can simply copy
> the
> > msvc directories. No need for a separate Makefile.am in alls directories.
>     Hmm, couldn't this be applied to everything, I mean I can't see a file
> in the CVS repository that should not be in the "release" tarball.
>

Sometimes you may  have files in the CVS repository you do not want in a
release: e.g. new, immature classes that are not ready for release yet.
But more importantly, make creates the dist tarball from a local checkout,
after ./configure has run. At this time the dirtree contains localized
generates files, like Makefiles, config.h and maybe other stuff as well.
Furthermore all kind of other stuff generated during development, like core
dumps, editor backups, patch rejects, etc., etc. occuppy the dir tree as well.
So one would have to be selective about what to copy and what not, anyway.
In general I think it's better if one consciously choose what goes in the dist
and what not.

Bastiaan

>
>     Baptiste.
> ---
> Baptiste Lepilleur <gai...@fr...>   http://gaiacrtn.free.fr/index.html
> Author of The Text Reformatter, a tool for fanfiction readers and writers.
> Language: English, French (Well, I'm French).
>
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> http://lists.sourceforge.net/lists/listinfo/cppunit-devel