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

[Baptiste L. <bl...@cl...>]

> 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, 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.

    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).