Fw: [Cppunit-devel] Re: [CppUnit] New repository layout...

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

    This is the mail I sent yesterday evening that did not get through:

> OK, I've merged this patch, it's in CVS now.
> A note for if you add project files in the future:
> simply adding them to CVS will not ensure that they end up in the dist
tarball
> as well. To get them in, they need to be added to the EXTRA_DIST variable
in
> the Makefile.am file in the same directory. For example
cppunit/Makefile.am
> contains:
>
> EXTRA_DIST = cppunit.dsw cppunit.dsp
Well, I'll do that for the next patch.

> >   How do you apply a patch? understand: what are the magic options ;-) ?
> >
>
> That's easy:
>
> cd topdir
> patch -p1 < improvement.patch
>
> The '-pN' option will strip N slashes from the front of filenames. So
with -p1,
> cppunit/cppunit/cppunit.dsp becomes cppunit/cppunit.dsp.
        Thanks you very much !

> >   - adding Michael's Feather framework/extensions back into the project.
> > What should be the physical layout ? include/cppunit/extensions ?
>
> That makes sense. Same as X11/extensions
        I have it ready. I need to make the patch, but that'll be for
tomorow (I hope).
        I've put the thing as follow:
        examples/msvc6/HostApp        for Michael Feather's original sample
(with change for compilation, of course)
        include/msvc6/testrunner/TestRunnerDlg.h    for the test runner
include. I'm not sure its the right way. When using cppunit, you need to add
2 paths. Perhaps it would be better to use different name for each platform:
include/testrunner-vc ? We have to think about the future test runner,
what's the planned layout ?
        src/msvc6/testrunner        for the testrunner dynamic library. The
library is build to lib/testrunnerd.dll and lib/testrunnerd.lib.

> I didn't have a look at the registry patch yet, I'll let you know when I
have.
    Hummm, I've been thinking about the registry a lot lately... One of the
reason, I've used the original version of the testrunner is that when you
pass the test to the runner, you grant him the ownership of those tests. The
registry owns the tests. It's incompatible.
    So you might as well kill it (I'll still be using a registry, but not a
test registry. Probably something like a suite factory registry). Thought
you might want to apply the patch since it remove the registry usage for the
TestCase (and fixes the doc).
---
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).