cppunit-devel

[Cppunit-devel] A few notes about my first experience with cppunit.

[Ferdinando A. <fer...@am...>]

Hi all

I maintain the QuantLib project (http://quantlib.org). QuantLib is a cross 
platform (Win32, *nix, Mac) cross compiler (Visual Studio, Borland, gcc, 
etc.) C++ library for quantitave finance.

QuantLib is also available as Python extension, and QuantLib-Python has a 
Python unit test suite. We heavily rely on this suite to test the 
underlying C++ layer.
As QuantLib and QuantLib-Python (may) have separate development I would 
like to add a pure C++ unit test suite.

A few notes about my first cppunit experience:

1) You may consider updating the C++ links at 
http://www.xprogramming.com/software.htm. This page points to the old 
versions of cppunit. I toyed with them, and I was going to write to the 
authors about setting up a sourceforge project.
I checked the availability of cppunit.sourceforge.net and - bingo! - I 
found the active project.
A "c++ unit test" search on google is of no help (except it points to 
http://sourceforge.net/projects/unittest/)

2) I opened TestRunner.dsw and I tried to compile the project TestRunner.
The first errors were because of the inclusion directive
#include <cppunit/extensions/TestDecorator.h>
Adding the cppunit/include path to the project didn't help, I had to add it 
to my VS settings, as if I had installed cppunit (probably because of the <>)
Then I got linking errors. If I've been naive please help me (I can post 
the error messages if needed)

3) I switched to cygwin for the usual configure-make dance.
Configure was OK, make failed since cygwin do not recognize my doxygen 
installation (this is a different problem: cygwin fails to use programs 
under "Program Files", probably because of the blank space).
I would humbly suggest to have a different directive for document 
generation, something like:
if DOXYGEN_FOUND
docs:
	$(DOXYGEN) Doxyfile.in
else
docs:
	echo You need to install doxygen in order to generate documentation.
endif

4) It would be nice to have a Win32 binary visual installer. This can be 
easily supported with NSIS (http://www.nullsoft.com/free/nsis/). NSIS is 
free and it is script driven. I could help creating the cppunit installer 
script, if somebody help me to select which *.h is needed, etc.

One last question: why there is a separate include and source folder for msvc6

In the meantime I'm switching to my Mandrake Linux box ....


ciao -- Nando

Re: [Cppunit-devel] A few notes about my first experience with cppunit.

[Steve M. R. <ste...@vi...>]

Hi Ferdinando,

I think all the points you raise are good ones.  I trust that the folks who can
update web pages will do so.  I don't use the windows platform, but I'm sure
that if you can submit patches to implement the ideas you suggest, they will be
considered seriously.

I would suggest that you use the CVS version of CppUnit, and keep abreast of
this mailing list, as the API, such as it is, is very fluid at the moment.


On Mon, Jul 16, 2001 at 04:01:19PM +0200, Ferdinando Ametrano wrote:

> 3) I switched to cygwin for the usual configure-make dance.
> Configure was OK, make failed since cygwin do not recognize my doxygen 
> installation (this is a different problem: cygwin fails to use programs 
> under "Program Files", probably because of the blank space).

When you say "make failed", do you mean that it really stopped with an
error message?  Or do you mean that it failed to generate the documentation?

> I would humbly suggest to have a different directive for document 
> generation, something like:
> if DOXYGEN_FOUND
> docs:
> 	$(DOXYGEN) Doxyfile.in
> else

Something similar to this is done.  Err, maybe only in CVS, though...


-Steve

-- 
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants

Re: [Cppunit-devel] A few notes about my first experience with cppunit.

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

----- Original Message -----
From: "Ferdinando Ametrano" <fer...@am...>
To: <cpp...@li...>
Sent: Monday, July 16, 2001 4:01 PM
Subject: [Cppunit-devel] A few notes about my first experience with cppunit.


> 2) I opened TestRunner.dsw and I tried to compile the project TestRunner.
> The first errors were because of the inclusion directive
> #include <cppunit/extensions/TestDecorator.h>
> Adding the cppunit/include path to the project didn't help, I had to add
it
> to my VS settings, as if I had installed cppunit (probably because of the
<>)
> Then I got linking errors. If I've been naive please help me (I can post
> the error messages if needed)
    Another user have reported having problem compiling cppunit 1.5.5. The
problem did not occur for him using the CVS version.  That problem kind of
bother me since it does seem to occurs only for a few people. I've never
been able to reproduce it either at work or at home). What's your
configuration ?

>
> 4) It would be nice to have a Win32 binary visual installer. This can be
> easily supported with NSIS (http://www.nullsoft.com/free/nsis/). NSIS is
> free and it is script driven. I could help creating the cppunit installer
> script, if somebody help me to select which *.h is needed, etc.
    What would this bring for the user ? I'd rather have a tar ball or a zip
file which I can explore than a big binary platform specific file.  End user
of the library are developer, so I don't think they have too much problem
depacking a file ;-) What is really missing is some guide (what project is
what, how to build it...) :-(...
    The tar ball "maker" already use a mecanism to select which file are
needed, so I'd rather not want to duplicate the work each time a file is
added (we forgot often enough as it is), unless there is some really meaning
value for it.

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