cppunit-devel — CppUnit Developer Mailing List

Re: [Cppunit-devel] Configuring CppUnit on HP-UX

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

On Sun, Apr 28, 2002 at 04:21:01PM +0300, Sha...@in... wrote:

> Now, the CppUnit configure script assumes that if the compiler
> supports namespaces, then the standard library is in namespace
> std. 

In fact, there are a couple of problems that are perhaps being conflated.

The configure script does check for namespace support.  Currently,
however, the only effect of namespace support is that some of the
other configure tests add "using namespace std;" to the test program.
So you may end up with the wrong result for the following preprocessor
symbols 
	HAVE_SSTREAM
	HAVE_CLASS_STRSTREAM
	FUNC_STRING_COMPARE_STRING_FIRST

Check in include/cppunit/config-auto.h, and edit by hand, if necessary.

The second -- much larger -- problem is that CppUnit assumes
unconditionally that the standard library is in namespace std.
[Yes, the result of the namespace test is ignored :-(]

> I've been thinking that I should solve this by adding a header
> file defining namespace std, and including in it (with "using"
> declarations) every name the compiler will complain about.
> 
> Are there better options?

I don't know.  The suggestion to #define std to empty seems like
less work, if it indeed fixes all the problems.  

It would be nice to have this detected and handled automatically, if
possible.  I suggest you open a bug report on this (be sure to include
the URL of this thread, for reference).


> Are there solutions to this problem in the more recent versions of
> CppUnit? 1.6.2 works fine for me in the other environments, and
> upgrading on four platforms is a cost I would much rather avoid.

Nothing in this area has changed in recent versions.

-S

-- 
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] Configuring CppUnit on HP-UX

[Jornei V. <jo...@co...>]

Hi,

    I'm using CppUnit 1.6.2 in HP-UX (11). We had to make some changes in
the code to make it possible to run and, concerning the 'std', we defined
std as empty in the compiler (-Dstd= ).
    I ported also the CppUnit 1.8.0 to HP-UX, with the same approach. It is
not the best thing to do since it leaves me with other issues that I'm
solving when they occur.

Jornei
----- Original Message -----
From: <Sha...@in...>
To: <cpp...@li...>
Cc: <sh...@pl...>
Sent: Sunday, April 28, 2002 9:21 AM
Subject: [Cppunit-devel] Configuring CppUnit on HP-UX


Hi guys,

First of all, I would like to thank you for producing this great library.

I am using CppUnit 1.6.2 for unit-testing a library developed on Win32 and 3
Unices (Solaris, HP, and AIX). I am having some problems with the HP side,
because there seems to be a unique configuration there: the compiler itself
does support namespaces, but the standard libraries are configured _not_ to
use namespace std (in newer compiler releases, there are better libraries,
but I am bound to the older ones by backward-compatibility requirements).

Now, the CppUnit configure script assumes that if the compiler supports
namespaces, then the standard library is in namespace std. I've been
thinking that I should solve this by adding a header file defining namespace
std, and including in it (with "using" declarations) every name the compiler
will complain about.

Are there better options?
Are there solutions to this problem in the more recent versions of CppUnit?
1.6.2 works fine for me in the other environments, and upgrading on four
platforms is a cost I would much rather avoid.

Thanks in advance,

Shai.


_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel

[Cppunit-devel] Configuring CppUnit on HP-UX

[<Sha...@in...>]

Hi guys,

First of all, I would like to thank you for producing this great =
library.

I am using CppUnit 1.6.2 for unit-testing a library developed on Win32 =
and 3 Unices (Solaris, HP, and AIX). I am having some problems with the =
HP side, because there seems to be a unique configuration there: the =
compiler itself does support namespaces, but the standard libraries are =
configured _not_ to use namespace std (in newer compiler releases, there =
are better libraries, but I am bound to the older ones by =
backward-compatibility requirements).

Now, the CppUnit configure script assumes that if the compiler supports =
namespaces, then the standard library is in namespace std. I've been =
thinking that I should solve this by adding a header file defining =
namespace std, and including in it (with "using" declarations) every =
name the compiler will complain about.

Are there better options?
Are there solutions to this problem in the more recent versions of =
CppUnit? 1.6.2 works fine for me in the other environments, and =
upgrading on four platforms is a cost I would much rather avoid.

Thanks in advance,

	Shai.

RE: [Cppunit-devel] Problem with CppUnit 1.8 linking on Solaris

[Stanley S. <su...@t-...>]

I'm still working on getting a good compile, and learning about autoconf =
and automake.  The -z now didn't help.  I could get reid of the warnings =
about the -Wp,-MD,... by adding an "AUTOMAKE_OPTIONS 1.4 =
no_dependencies" to the beginning of every Makefile.am file that didn't =
have that macro definiton already by hand, and adding the =
"no_dependancies" to the master Makefile.am file's AUOTOMAKE_OPTIONS.  =
I'm trying to clean that up so that I can define a macro =
(solaris_forte_AUTOMAKE_OPTIONS, maybe?) that autoconf can set if it =
determines that you're compiling with the Forte compiler.  The Auotmake =
people say that they do not support dependancy generation on anything =
but the GNU compiler.  I was able to compile the 1.6 versions and use =
it, but I am trying to work my way through the template problems and fix =
them for the more recent build.  It's just not working yet. :-(  I =
really need the test drivers working again.



-----Original Message-----

From:	Gerard Benenyan [mailto:Ger...@jp...]

Sent:	Thu 25-Apr-02 17:25

To:	cpp...@li...

Cc:=09

Subject:	[Cppunit-devel] Problem with CppUnit 1.8 linking on Solaris


Hello,



This is regarding : [ 544864 ] fails to build for SUN Forte C++



Some one indicated a possible solution, but it does not

seem to work for me.



Does anyone have a Makefile for the Sun platform that actually

works?  I would appreciate a copy.



Or if there is Sun binaries available, that would be even better.



Thanks.



Gerard B.



---------------------------------------------------------------------

Gerard Benenyan                         TES Ground System - Key Staff

Office: T1721-221                       Jet Propulsion Laboratory

Phone:  (818) 393-7791                  M.S. 169-315

Fax:    (818) 393-6962                  4800 Oak Grove Drive

E-mail: ger...@jp...    Pasadena. CA  91109

---------------------------------------------------------------------





_______________________________________________

Cppunit-devel mailing list

Cpp...@li...

https://lists.sourceforge.net/lists/listinfo/cppunit-devel

[Cppunit-devel] Problem with CppUnit 1.8 linking on Solaris

[Gerard B. <Ger...@jp...>]

Hello,

This is regarding : [ 544864 ] fails to build for SUN Forte C++

Some one indicated a possible solution, but it does not
seem to work for me.

Does anyone have a Makefile for the Sun platform that actually
works?  I would appreciate a copy.

Or if there is Sun binaries available, that would be even better.

Thanks.

Gerard B.

---------------------------------------------------------------------
Gerard Benenyan                         TES Ground System - Key Staff
Office: T1721-221                       Jet Propulsion Laboratory
Phone:  (818) 393-7791                  M.S. 169-315
Fax:    (818) 393-6962                  4800 Oak Grove Drive
E-mail: ger...@jp...    Pasadena. CA  91109
---------------------------------------------------------------------

Re: [Cppunit-devel] [Bug] Xml outputer

[Baptiste L. <gai...@fr...>]

Fixed, DllPlugInTester was giving the encoding provided by the command line
parser, even if it was an empty string. Solved this by making XmlOutputter
smarter (empty = default encoding).

Thanks,
Baptiste.


----- Original Message -----
From: "Philippe Lavoie" <phi...@ca...>
To: <cpp...@li...>
Sent: Thursday, April 25, 2002 2:01 AM
Subject: [Cppunit-devel] [Bug] Xml outputer



The XML outputer generates something like

<?xml version="1.0" encoding='' standalone='yes' ?>
<TestRun>
  <FailedTests>
    <FailedTest id="8">

IE chokes on the invalid '' delimeters and it also chokes on an invalid
encoding value (empty).

I'll correct it soon, I just wanted to report it for now as I also have to
leave now :)

Phil

_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel

Re: [Cppunit-devel] Patch to ask user before exiting cppunit

[Baptiste L. <gai...@fr...>]

I integrated the patch. Here is a slighty easier way to wait for enter (it's
what we used in 1.6.2 TextTestRunner):
    std::cout << "Please press <RETURN> to exit" << std::endl;
    std::cin.get();

Oh, and I renamed the option to -w --wait, which I believe is more
intuitive.

Thanks,
Baptiste.


----- Original Message -----
From: "Philippe Lavoie" <phi...@ca...>
To: <cpp...@li...>
Sent: Thursday, April 25, 2002 1:54 AM
Subject: [Cppunit-devel] Patch to ask user before exiting cppunit



 Hi all,

I created a patch to cppunit (cvs version) that allows one to specify -a
(or --ask) to the DllPluginTesterd.exe program.

The idea is that I've added DllPluginTesterD.exe as an external tool and
with this option I get to see the output before the windows exits :)
Sometimes just getting 1, is not enough to find out what the error is.

The only thing it does is it asks you to press enter before it exits under
normal conditions.

Phil

PS Man it's hard to find a way to implement 'press any key'. I have to
specify 'press enter'. Stupid istream...

[Cppunit-devel] [Bug] Xml outputer

[Philippe L. <phi...@ca...>]

The XML outputer generates something like

<?xml version=3D"1.0" encoding=3D'' standalone=3D'yes' ?>
<TestRun>
  <FailedTests>
    <FailedTest id=3D"8">

IE chokes on the invalid '' delimeters and it also chokes on an invalid =
encoding value (empty).

I'll correct it soon, I just wanted to report it for now as I also have =
to leave now :)

Phil=20

[Cppunit-devel] Patch to ask user before exiting cppunit

[Philippe L. <phi...@ca...>]

 Hi all,

I created a patch to cppunit (cvs version) that allows one to specify -a =
(or --ask) to the DllPluginTesterd.exe program.

The idea is that I've added DllPluginTesterD.exe as an external tool and =
with this option I get to see the output before the windows exits :)  =
Sometimes just getting 1, is not enough to find out what the error is.

The only thing it does is it asks you to press enter before it exits =
under normal conditions.

Phil

PS Man it's hard to find a way to implement 'press any key'. I have to =
specify 'press enter'. Stupid istream...

[Cppunit-devel] How do I compile my VC6 Unit test project with "use MFC in a static library"?

[Steve H. <ste...@im...>]

Hi there
	I try to create a VC++6 unit test project that uses CppUnit and =
TestRunner library. If I compile the program with "use MFC in a shared =
DLL", that is OK.  But when I compile the program with "use MFC in a =
static library", I got errors such as "libc.lib(crt0dat.obj) : error =
LNK2005: _exit already defined in msvcrt.lib(MSVCRT.dll)
libc.lib(crt0dat.obj) : error LNK2005: __exit already defined in =
msvcrt.lib(MSVCRT.dll)"
Or=20
"nafxcw.lib(appcore.obj) : error LNK2001: unresolved external symbol =
___argv
nafxcw.lib(appcore.obj) : error LNK2001: unresolved external symbol =
___argc
nafxcw.lib(timecore.obj) : error LNK2001: unresolved external symbol =
__mbctype"

I tried to recompile the examples come with CppUnit.  I got similar =
errors.  Could you tell me why and how I can fix the problem?  Thanks,

Steve Hong

=09

RE: [Cppunit-devel] How to use clocker in my own project ?

[Tredinnick, J. <jac...@me...>]

Well,

I've been interested in timing of CppUnit tests for a while - so here's my
2p worth ;)

I think the reason for questioning timing of unit tests is that this sort of
thing "should be" done with batch mode tests (i.e. where your app is invoked
batch mode, once per test) as opposed to unit tests.  Assuming, that is that
you have a batch interface for your app.

I guess this is because the things you want to time are generally specific
bits of functionality, rather than say only a particular method of a class
(which is usually too fast).

Personally I don't see anything wrong with calling larger bits of
functionality as unit tests, or even stress-testing lower level things like
file copying routines and such.  Where to draw the line between unit tests
and batch mode tests is a personal choice (and a can of worms;)

For these larger unit tests, the inaccuraries of the NT (and I believe UNIX)
clock() calls are reasonable for operations that take several seconds of
CPU.

In this sense I would suggest that timing of tests is sometimes relevant to
have per-test but not particularly relevant for the whole test run.

Regards
--
Jake


-----Original Message-----
From: Philippe Lavoie [mailto:phi...@ca...]
Sent: 23 April 2002 15:08
To: Baptiste Lepilleur; cpp...@li...
Subject: RE: [Cppunit-devel] How to use clocker in my own project ?


I want to use the timing for statistics. Often developpers will do a small
change that has a big impact on performance, they added expensive
copy-constructors or other such nuisance.

I just want to keep track of the overall progress of the timings. I'm using
cppunit as part of an integrated build process based on ant. At every hours
or so, the build process finds out if there is something new. It then
compiles and runs the tests. A new result-YYYYMMDDHHMM.xml file is created. 

The build process then merges the information with the other result-XXXXX
files. A graph of the timings can be made, and other statistical information
too (number of line of codes changed, number of tests added, etc.). 

Whether this is really important, I don't know. I just know that we
shouldn't be making things slower as we progress and that catching this as
part of the build process is as a good place as any other :)

Phil

PS This comes from one of our clients where the test stress every bugfix to
see if a fix comes with a speed degradation cost. 

> -----Original Message-----
> From: Baptiste Lepilleur [mailto:gai...@fr...]
> Sent: Tuesday, April 23, 2002 9:42 AM
> To: cpp...@li...
> Subject: Re: [Cppunit-devel] How to use clocker in my own project ?
> 
> 
> Clocker was note designed for 'real life' project (just an 
> example of weird
> stuff you can do with the TestListener). As you may have 
> noticed, reported
> time are far from accurate (even using the supposed high 
> precision timer of
> Nt 100 nanosecond, you don't get anything better that a 10ms 
> resolution).
> 
> Still you raise an interesting problem. I can think of two 
> ways of doing
> what you want at the current time:
> - Clocker write a second XML file, it is later merged with 
> the first one
> (using XSL or whatever)
> - Extending XmlOutputter in Clocker to write the Xml ouput 
> with test time.
> 
> What are you using test time for ? I don't really see any use 
> to this (total
> test time yes, but individual...)
> 
> You're right about the average test time bug: the time of the 
> test case is
> counted twice: for the test and the suite... I'll fix that.
> 
> Baptiste.
> 
> ----- Original Message -----
> From: "Philippe Lavoie" <phi...@ca...>
> To: <cpp...@li...>
> Sent: Tuesday, April 23, 2002 1:25 AM
> Subject: [Cppunit-devel] How to use clocker in my own project ?
> 
> 
> 
> Hi guys,
> 
> Now that I've managed to figure out how to do a proper copy 
> from one place
> to the other :) I'm ready to incorporate cppunit results 
> inside the build
> process (I'm using ant to do the builds).
> 
> I'd prefer to have the xml output with the test duration 
> times included. I
> want to have the default XML output from DllPluginTester to 
> also have timing
> values. What is the best way to achieve this ?
> 
> I think I might be missing some basic concepts on how I can 
> mix and match
> the different listener and outputer. I'm pretty sure I should 
> look at the
> ClockPlugIn for guidance.
> 
> I did the following naive test hoping that some magic would occur
> 
> DllPlugInTesterd_dll -x test.xml -c Mine.dll clockerplugind.dll
> .
> (0.050s) All Tests
>    +--(0.050s) InputErrorTest
>    |  +--(0.050s) InputErrorTest.testNormalUsage
> 
> Total elapsed time: (0.050s) , average test case time: (0.150s) OK (1)
> 
> The command line output is indeed magic :) (although there is 
> a bug in the
> average test case time). However, the XML output is as follows.
> 
> 
> <?xml version="1.0" encoding='' standalone='yes' ?>
> <TestRun>
>   <FailedTests></FailedTests>
>   <SuccessfulTests>
>     <Test id="1">
>       <Name>InputErrorTest.testNormalUsage</Name>
>     </Test>
>   </SuccessfulTests>
>   <Statistics>
>     <Tests>1</Tests>
>     <FailuresTotal>0</FailuresTotal>
>     <Errors>0</Errors>
>     <Failures>0</Failures>
>   </Statistics>
> </TestRun>
> 
> Please let me know if you know in which direction I should go 
> to add a time
> attribute to the Test results. Thanks.
> 
> 
> Phil
> 
> 
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
> 
> 
> 
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
> 

_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel

RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem

[Stanley S. <su...@t-...>]

I'll give that a try, if I can figure out where to supply arguments to =
automake.  I'm not that familar with the GNU auto* tools, we use a =
combination of perl and shell scripts to maintain our multi-platform =
build system.  It has the advantage of being much faster, but the =
disadvantage of being tailored to supporting our own system, not anyone =
else's.



-----Original Message-----

From:	Steve M. Robbins [mailto:ste...@vi...]

Sent:	Mon 22-Apr-02 17:59

To:	Stanley Sutton

Cc:	CppUnit Development

Subject:	Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem


On Mon, Apr 22, 2002 at 12:38:25PM -0500, Stanley Sutton wrote:



> Also, the "-Wp,-MD,.deps/..." doesn't

> seem to mean anything to the Solaris compiler, so the cp and the tr =
both fail.=20

> If the purpose of the option is to generat dependancies, the -xM =
generates a

> dependancy list to stdout, -xM1 generates a unique list with the =
/usr/include

> files filtered out.



Yes, that is the dependency-generating stuff from automake.



I can't quickly find a list of compilers that automake supports, but it

sounds like yours is not one of them.  The automake team would probably

like to know how to enable it for your compiler; send them email at

<bug...@gn...>.



In the meantime, automake supports a --disable-dependency-tracking

that you can use.  This may not be supported in automake versions

prior to 1.5.







On Mon, Apr 22, 2002 at 02:37:42PM -0500, Stanley Sutton wrote:



> As near as I can figure, the problem is in the template instantation.  =
I know

> we've had problems with that in our code before, do to a compiler =
inker bug.=20

> We use the linker option "-z now" on all of our Solaris compiles, as =
well as

> absolute disk paths rather than relative ones to keep from confusing =
the

> compiler/linker.  However, I haven't been able to figure out how to =
add the "-z

> now" to the linker.  ".configure =
--prefix-/space/local_users/sutton/solaris

> LD_FLAGS=3D'-z now'" didn't seem to have any affect.



The variable is "LDFLAGS". =20



Setting it at configure time should work with autoconf 2.5x, I

believe.  If it doesn't, you can always set it on the "make" command

line.









--=20

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





_______________________________________________

Cppunit-devel mailing list

Cpp...@li...

https://lists.sourceforge.net/lists/listinfo/cppunit-devel

RE: [Cppunit-devel] How to use clocker in my own project ?

[Philippe L. <phi...@ca...>]

I want to use the timing for statistics. Often developpers will do a =
small change that has a big impact on performance, they added expensive =
copy-constructors or other such nuisance.

I just want to keep track of the overall progress of the timings. I'm =
using cppunit as part of an integrated build process based on ant. At =
every hours or so, the build process finds out if there is something =
new. It then compiles and runs the tests. A new result-YYYYMMDDHHMM.xml =
file is created.=20

The build process then merges the information with the other =
result-XXXXX files. A graph of the timings can be made, and other =
statistical information too (number of line of codes changed, number of =
tests added, etc.).=20

Whether this is really important, I don't know. I just know that we =
shouldn't be making things slower as we progress and that catching this =
as part of the build process is as a good place as any other :)

Phil

PS This comes from one of our clients where the test stress every bugfix =
to see if a fix comes with a speed degradation cost.=20

> -----Original Message-----
> From: Baptiste Lepilleur [mailto:gai...@fr...]
> Sent: Tuesday, April 23, 2002 9:42 AM
> To: cpp...@li...
> Subject: Re: [Cppunit-devel] How to use clocker in my own project ?
>=20
>=20
> Clocker was note designed for 'real life' project (just an=20
> example of weird
> stuff you can do with the TestListener). As you may have=20
> noticed, reported
> time are far from accurate (even using the supposed high=20
> precision timer of
> Nt 100 nanosecond, you don't get anything better that a 10ms=20
> resolution).
>=20
> Still you raise an interesting problem. I can think of two=20
> ways of doing
> what you want at the current time:
> - Clocker write a second XML file, it is later merged with=20
> the first one
> (using XSL or whatever)
> - Extending XmlOutputter in Clocker to write the Xml ouput=20
> with test time.
>=20
> What are you using test time for ? I don't really see any use=20
> to this (total
> test time yes, but individual...)
>=20
> You're right about the average test time bug: the time of the=20
> test case is
> counted twice: for the test and the suite... I'll fix that.
>=20
> Baptiste.
>=20
> ----- Original Message -----
> From: "Philippe Lavoie" <phi...@ca...>
> To: <cpp...@li...>
> Sent: Tuesday, April 23, 2002 1:25 AM
> Subject: [Cppunit-devel] How to use clocker in my own project ?
>=20
>=20
>=20
> Hi guys,
>=20
> Now that I've managed to figure out how to do a proper copy=20
> from one place
> to the other :) I'm ready to incorporate cppunit results=20
> inside the build
> process (I'm using ant to do the builds).
>=20
> I'd prefer to have the xml output with the test duration=20
> times included. I
> want to have the default XML output from DllPluginTester to=20
> also have timing
> values. What is the best way to achieve this ?
>=20
> I think I might be missing some basic concepts on how I can=20
> mix and match
> the different listener and outputer. I'm pretty sure I should=20
> look at the
> ClockPlugIn for guidance.
>=20
> I did the following naive test hoping that some magic would occur
>=20
> DllPlugInTesterd_dll -x test.xml -c Mine.dll clockerplugind.dll
> .
> (0.050s) All Tests
>    +--(0.050s) InputErrorTest
>    |  +--(0.050s) InputErrorTest.testNormalUsage
>=20
> Total elapsed time: (0.050s) , average test case time: (0.150s) OK (1)
>=20
> The command line output is indeed magic :) (although there is=20
> a bug in the
> average test case time). However, the XML output is as follows.
>=20
>=20
> <?xml version=3D"1.0" encoding=3D'' standalone=3D'yes' ?>
> <TestRun>
>   <FailedTests></FailedTests>
>   <SuccessfulTests>
>     <Test id=3D"1">
>       <Name>InputErrorTest.testNormalUsage</Name>
>     </Test>
>   </SuccessfulTests>
>   <Statistics>
>     <Tests>1</Tests>
>     <FailuresTotal>0</FailuresTotal>
>     <Errors>0</Errors>
>     <Failures>0</Failures>
>   </Statistics>
> </TestRun>
>=20
> Please let me know if you know in which direction I should go=20
> to add a time
> attribute to the Test results. Thanks.
>=20
>=20
> Phil
>=20
>=20
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
>=20
>=20
>=20
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
>=20

RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem

[Stanley S. <su...@t-...>]

It forces the linker to us ld instead of ild, and forces  using =
templates in the library defined, rather than deferring to last possible =
moment.  I think it's similar to creating a "closed library" on HP.  I =
know on our software at work, we have to use it to make our libraries =
function correctly (we create about 10 shared libraries on the way to =
creating our executable, and it never worked correctly until we added =
the option.  We've reported the problem to Sun, but haven't gotten any =
feedback on it).



-----Original Message-----

From:	Baptiste Lepilleur [mailto:gai...@fr...]

Sent:	Mon 22-Apr-02 16:17

To:	Stanley Sutton; cpp...@li...

Cc:=09

Subject:	Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem


I don't have a clue on how to do that (I know barely enough to update =
the

automake/autoconf stuffs for each release).



A tempory fix that might work would be to edit

src/DllPlugInTester/makefile.am and

add your flag to:

DllPlugInTesterTest_LDFLAGS =3D -ldl



What is that '-z now' option supposed to do ? This might bring some =
light

about the source of the problem.



Baptiste.



----- Original Message -----

From: "Stanley Sutton" <su...@t-...>

To: "Baptiste Lepilleur" <gai...@fr...>;

<cpp...@li...>

Sent: Monday, April 22, 2002 9:37 PM

Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem







Here's the latest problem:



gmake[2]: Entering directory

`/space/local_users/sutton/projects/cppunit/src/DllPlugInTester'

/bin/bash ../../libtool --mode=3Dlink CC  -g  -o DllPlugInTester -ldl

DllPlugInTester.o CommandLineParser.o ../../src/cppunit/libcppunit.la

CC -g -o .libs/DllPlugInTester DllPlugInTester.o CommandLineParser.o  =
-ldl

../../src/cppunit/.libs/libcppunit.so -R/home/sutton/solaris/lib

ild: (undefined symbol) unsigned

std::deque<CppUnit::TestFailure*,std::allocator<CppUnit::TestFailure*>

>::__buffer_size() -- referenced in =
../../src/cppunit/.libs/libcppunit.so

ild: (undefined symbol)

std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::iterator

std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*>

>::erase(std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*>

>::iterator,std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*>

>::iterator) -- referenced in ../../src/cppunit/.libs/libcppunit.so

(plus many, many more in the same vein)



As near as I can figure, the problem is in the template instantation.  I

know we've had problems with that in our code before, do to a compiler =
inker

bug.  We use the linker option "-z now" on all of our Solaris compiles, =
as

well as absolute disk paths rather than relative ones to keep from =
confusing

the compiler/linker.  However, I haven't been able to figure out how to =
add

the "-z now" to the linker.

 ".configure --prefix-/space/local_users/sutton/solaris LD_FLAGS=3D'-z =
now'"

didn't seem to have any affect.







-----Original Message-----



From: Baptiste Lepilleur [mailto:gai...@fr...]



Sent: Mon 22-Apr-02 11:24



To: Stanley Sutton; cpp...@li...



Cc:



Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem





Did you follow the step indicated in Readme.CVS (and if those don't =
work,



did you try the lastest tar ball ?):







* Unix:







To generate the configure script, you need several auxiliary



tools.  The version numbers are minimal: later versions should



also work.







 autoconf 2.50



 - see http://www.gnu.org/directory/autoconf.html







 automake 1.4



 - see http://www.gnu.org/directory/automake.html







 libtool 1.4



 - see http://www.gnu.org/directory/libtool.html











After checking the sources out from CVS, you need to run the script







 sh autogen.sh







from the top-level source directory (i.e. the one containing this



file).  This needs only to be done once.







Baptiste.







----- Original Message -----



From: "Stanley Sutton" <su...@t-...>



To: "Baptiste Lepilleur" <gai...@fr...>;



<cpp...@li...>



Sent: Monday, April 22, 2002 5:36 PM



Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem















I'm still having some problmes on Solaris 8, using the Forte 6 compiler. =
 I



removed all my local files and got a fresh CVS snapshot.  Here's there =
first



error:







cd . && autoconf



autoconf: warning: both `configure.ac' and `configure.in' are present.



autoconf: warning: proceeding with `configure.ac'.







configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see



section `AC_LIBOBJ vs. LIBOBJS'







I'm using GNU make, by the way, as well as the GNU versions of most of =
the



utilities.















-----Original Message-----







From: Baptiste Lepilleur [mailto:gai...@fr...]







Sent: Sun 21-Apr-02 08:28







To: cpp...@li...







Cc:







Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball











    New snapshot. The problem on Unix should be fixed. Thanks to all =
those







who helped !















       KNOWN PROBLEMS:







- TestPlugIn project has not been removed from the Examples workspace =
(just







click cancel)







- Money example is missing dependency with cppunit.dsp















    As usal, the snapshop can be found at:















http://cppunit.sourceforge.net/snapshot/







http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz







http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz















 New in CppUnit 1.9.6:







 ----------------------















 - DllPlugInTester can be parametrized from command line







 - Two test listener plug-in examples







 - An 'hello world' example & getting started document : Money







 - Contribution: generic makefile for Borland 5.5 free compiler.







 - Bug fixes















* DllPlugInTester:















 - Advanced command line to support miscellaneous listener outputer.







   Parameters can now be passed to test plug-in:















  -c --compiler







   Use CompilerOutputter







  -x --xml [filename]







   Use XmlOutputter (if filename is omitted, then output to cout or







   cerr.







  -s --xsl stylesheet







   XML style sheet for XML Outputter







  -e --encoding encoding







   XML file encoding (UTF8, shift_jis, ISO-8859-1...)







  -b --brief-progress







   Use BriefTestProgressListener (default is TextTestProgressListener)







  -n --no-progress







   Show no test progress (disable default TextTestProgressListener)







  -t --text







   Use TextOutputter







  -o --cout







   Ouputters output to cout instead of the default cerr.







  filename[=3D"options"]







   Many filenames can be specified. They are the name of the







   test plug-ins to load. Optional plug-ins parameters can be







   specified after the filename by adding '=3D'.







  [:testpath]







   Optional. Only one test path can be specified. It must







   be prefixed with ':'. See TestPath constructor for syntax.















  'parameters' (test plug-in or XML filename, test path...) may contains







  spaces if double quoted. Quote may be escaped with \".















  Some examples of command lines:







DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll







CppUnitTestPlugInd.dll







  Will load 2 tests plug-ins (available in lib/), use the brief test







  progress, output the result in XML in file tests.xml and also







  output the result using the compiler outputter.















DllPlugInTesterd_dll.exe ClockerPlugInd.dll=3D"flat" -n =
CppUnitTestPlugInd.dll







  Will load the 2 test plug-ins, and pass the parameter string "flat"







  to the Clocker plug-in, disable test progress. Clocker being a test







  listener plug-ins (it doesn't implements any tests, it just register







  a TestListener), this is equivalent to say 'run all the test







  of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'.















DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core







  Will run the test named "Core" (a suite in the present case ) of the







  test plug-in.















* Documentation















 - New getting started documentation. Not completed yet, but probably







   a good complement to the current cookbook. Explore the creation







   of the Money example.















* Examples















 - Money (examples/Money): the 'hello world' example. Unit tests for







   a simple Money class.















 - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp):







   unit tests for CommandLineParser. Not really an example, but only







   slightly more complex than Money.















 - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in







   that track tests and test suites running time. Parameter: "flat"







   for a reporting with a flattened tree.















 - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that







   dump the test tree as it run. Paramater: "flat" for a reporting







   with a flattened tree.















 - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp):







   CppUnit's test suite as a test plug-in.















* Contribution















  - Contributed by project cuppa team







(http://sourceforge.jp/projects/cuppa/):















 - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not







   depend on a specific CppUnit version.















* Compatiblity breaks















 - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester







   command line.















* Bug Fix:















 - DynamicLibaryManager did not report the library name when loading a







   a library.















 - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki







   ('cuppa' project team).















 - Broken build on Unix should be fixed for most (thanks to







   Jeffrey Morgan).















    Enjoy,







    Baptiste.







---







Baptiste Lepilleur <gai...@fr...>







http://gaiacrtn.free.fr/























_______________________________________________







Cppunit-devel mailing list







Cpp...@li...







https://lists.sourceforge.net/lists/listinfo/cppunit-devel

Re: [Cppunit-devel] How to use clocker in my own project ?

[Baptiste L. <gai...@fr...>]

Clocker was note designed for 'real life' project (just an example of weird
stuff you can do with the TestListener). As you may have noticed, reported
time are far from accurate (even using the supposed high precision timer of
Nt 100 nanosecond, you don't get anything better that a 10ms resolution).

Still you raise an interesting problem. I can think of two ways of doing
what you want at the current time:
- Clocker write a second XML file, it is later merged with the first one
(using XSL or whatever)
- Extending XmlOutputter in Clocker to write the Xml ouput with test time.

What are you using test time for ? I don't really see any use to this (total
test time yes, but individual...)

You're right about the average test time bug: the time of the test case is
counted twice: for the test and the suite... I'll fix that.

Baptiste.

----- Original Message -----
From: "Philippe Lavoie" <phi...@ca...>
To: <cpp...@li...>
Sent: Tuesday, April 23, 2002 1:25 AM
Subject: [Cppunit-devel] How to use clocker in my own project ?



Hi guys,

Now that I've managed to figure out how to do a proper copy from one place
to the other :) I'm ready to incorporate cppunit results inside the build
process (I'm using ant to do the builds).

I'd prefer to have the xml output with the test duration times included. I
want to have the default XML output from DllPluginTester to also have timing
values. What is the best way to achieve this ?

I think I might be missing some basic concepts on how I can mix and match
the different listener and outputer. I'm pretty sure I should look at the
ClockPlugIn for guidance.

I did the following naive test hoping that some magic would occur

DllPlugInTesterd_dll -x test.xml -c Mine.dll clockerplugind.dll
.
(0.050s) All Tests
   +--(0.050s) InputErrorTest
   |  +--(0.050s) InputErrorTest.testNormalUsage

Total elapsed time: (0.050s) , average test case time: (0.150s) OK (1)

The command line output is indeed magic :) (although there is a bug in the
average test case time). However, the XML output is as follows.


<?xml version="1.0" encoding='' standalone='yes' ?>
<TestRun>
  <FailedTests></FailedTests>
  <SuccessfulTests>
    <Test id="1">
      <Name>InputErrorTest.testNormalUsage</Name>
    </Test>
  </SuccessfulTests>
  <Statistics>
    <Tests>1</Tests>
    <FailuresTotal>0</FailuresTotal>
    <Errors>0</Errors>
    <Failures>0</Failures>
  </Statistics>
</TestRun>

Please let me know if you know in which direction I should go to add a time
attribute to the Test results. Thanks.


Phil


_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel

RE: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET

[Philippe L. <phi...@ca...>]

It seems that the .h that came with 1.9.2 had an issue with stdafx.h.

I did more tests this morning with the cvs version, and everything is =
fine. I can put the stdafx.h before or after the include and everything =
works as it's suppose to.

Sorry if I gave you a scare :)

Phil

PS Maybe all the .h could have a version label in them so that I could =
see really easyilly that I'm looking at the wrong .h :)

> -----Original Message-----
> From: Baptiste Lepilleur [mailto:gai...@fr...]
> Sent: Tuesday, April 23, 2002 5:38 AM
> To: cpp...@li...
> Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET
>=20
>=20
> Could you still specify the trouble you add with stdafx.h.
>=20
> Thanks,
> Baptiste.
>=20
> ----- Original Message -----
> From: "Philippe Lavoie" <phi...@ca...>
> To: "Philippe Lavoie" <phi...@ca...>; "Baptiste=20
> Lepilleur"
> <gai...@fr...>; <cpp...@li...>
> Sent: Tuesday, April 23, 2002 12:54 AM
> Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET
>=20
>=20
> Never mind... I had a bad version of the Include files...
>=20
> Sigh... spent the whole afternoon on this... Stupid copy=20
> doesn't work when
> the file is in use... Stupid stupid stupid.
>=20
>=20

Re: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET

[Baptiste L. <gai...@fr...>]

Could you still specify the trouble you add with stdafx.h.

Thanks,
Baptiste.

----- Original Message -----
From: "Philippe Lavoie" <phi...@ca...>
To: "Philippe Lavoie" <phi...@ca...>; "Baptiste Lepilleur"
<gai...@fr...>; <cpp...@li...>
Sent: Tuesday, April 23, 2002 12:54 AM
Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET


Never mind... I had a bad version of the Include files...

Sigh... spent the whole afternoon on this... Stupid copy doesn't work when
the file is in use... Stupid stupid stupid.


Phil

> -----Original Message-----
> From: Philippe Lavoie
> Sent: Monday, April 22, 2002 6:24 PM
> To: Baptiste Lepilleur; cpp...@li...
> Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET
>
>
>
> Hi,
>
> I did a cvs update of cppunit and I can't get the testplugin
> to work for my own project. Everything compiles fine inside
> the examples .dsw. I can run them, life is good.
>
> I've defined CPPUNIT_DLL. Then, I added a cppunitplugin.cpp
> file with the following content
>
>  #include <cppunit/plugin/TestPlugIn.h>
>
>  CPPUNIT_PLUGIN_IMPLEMENT();
>
>  // needed for an ATL project
>  // note that cppunit fails if stdafx.h is included before the macro.
>  #include "stdafx.h"
>
>
> Finally, I link with cppunitd_dll.lib. It compiles... but it returns
>
> Failed to load test plug-in:
> Symbol [cppunitTestPlugIn] not found in dynamic libary:Bob.dll
>
>
> This is really weird as simple_plugin works like a charm and
> I can't see what the missing option could be.
>
> Please help
>
> Phil
>
>
>
>
>
>
>
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
>

Re: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET

[Baptiste L. <gai...@fr...>]

What version of CppUnit are you using ? TestPlugInDefaultImpl doesn't exist
anymore. Try switching to 1.9.6, there has been a lot of clean up in the
TestPlugIn stuff!

Baptiste.


----- Original Message -----
From: "Philippe Lavoie" <phi...@ca...>
To: "Philippe Lavoie" <phi...@ca...>; "Baptiste Lepilleur"
<gai...@fr...>; <cpp...@li...>
Sent: Tuesday, April 23, 2002 12:44 AM
Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET


I did a little bit more investigation, and if I use the following code in
cppunitplugin.cpp (inside my ATL project). The following is just the define
expanded.

#include "stdafx.h"
#include <cppunit/plugin/TestPlugIn.h>

class CppUnitTestPlugInNamedDefaultImpl : public
CppUnit::TestPlugInDefaultImpl


  virtual std::string getSuiteName()


      return "Acuraci";
    }
  };

extern "C" __declspec(dllexport) CppUnitTestPlugIn* cppunitTestPlugIn(void)


    static CppUnitTestPlugInNamedDefaultImpl plugIn;
    return &plugIn;
  }



I receive this instead...

CppUnitPlugin.obj : error LNK2001: unresolved external symbol "public:
virtual void __thiscall CppUnit::TestPlugInDefaultImpl::uninitialize(void)"
(?uninitialize@TestPlugInDefaultImpl@CppUnit@@UAEXXZ)
CppUnitPlugin.obj : error LNK2001: unresolved external symbol "public:
virtual class CppUnit::Test * __thiscall
CppUnit::TestPlugInDefaultImpl::getTestSuite(void)"
(?getTestSuite@TestPlugInDefaultImpl@CppUnit@@UAEPAVTest@2@XZ)
CppUnitPlugin.obj : error LNK2001: unresolved external symbol "public:
virtual void __thiscall CppUnit::TestPlugInDefaultImpl::initialize(void)"
(?initialize@TestPlugInDefaultImpl@CppUnit@@UAEXXZ)
CppUnitPlugin.obj : error LNK2019: unresolved external symbol
"__declspec(dllimport) public: __thiscall
CppUnit::TestPlugInDefaultImpl::TestPlugInDefaultImpl(void)"
(__imp_??0TestPlugInDefaultImpl@CppUnit@@QAE@XZ) referenced in function
"public: __thiscall
CppUnitTestPlugInNamedDefaultImpl::CppUnitTestPlugInNamedDefaultImpl(void)"
(??0CppUnitTestPlugInNamedDefaultImpl@@QAE@XZ)
CppUnitPlugin.obj : error LNK2019: unresolved external symbol
"__declspec(dllimport) public: virtual __thiscall
CppUnit::TestPlugInDefaultImpl::~TestPlugInDefaultImpl(void)"
(__imp_??1TestPlugInDefaultImpl@CppUnit@@UAE@XZ) referenced in function
"public: virtual __thiscall
CppUnitTestPlugInNamedDefaultImpl::~CppUnitTestPlugInNamedDefaultImpl(void)"
(??1CppUnitTestPlugInNamedDefaultImpl@@UAE@XZ)


It's not really an improvement but hopefully someone can help me get the
latest version of cppunit to work with Visual .NET's C++ ATL projects.

Phil

> -----Original Message-----
> From: Philippe Lavoie
> Sent: Monday, April 22, 2002 6:24 PM
> To: Baptiste Lepilleur; cpp...@li...
> Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET
>
>
>
> Hi,
>
> I did a cvs update of cppunit and I can't get the testplugin
> to work for my own project. Everything compiles fine inside
> the examples .dsw. I can run them, life is good.
>
> I've defined CPPUNIT_DLL. Then, I added a cppunitplugin.cpp
> file with the following content
>
>  #include <cppunit/plugin/TestPlugIn.h>
>
>  CPPUNIT_PLUGIN_IMPLEMENT();
>
>  // needed for an ATL project
>  // note that cppunit fails if stdafx.h is included before the macro.
>  #include "stdafx.h"
>
>
> Finally, I link with cppunitd_dll.lib. It compiles... but it returns
>
> Failed to load test plug-in:
> Symbol [cppunitTestPlugIn] not found in dynamic libary:Bob.dll
>
>
> This is really weird as simple_plugin works like a charm and
> I can't see what the missing option could be.
>
> Please help
>
> Phil
>
>
>
>
>
>
>
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
>

Re: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET

[Baptiste L. <gai...@fr...>]

Could you specify the failure you get when you include stdafx.h before
(windows.h is not supposed to be included if it has already been included) ?

Also, try putting all your dll (cppunitd.dll, dllplugintester.exe, bob.dll)
in the same directory to run it.

Baptiste.


----- Original Message -----
From: "Philippe Lavoie" <phi...@ca...>
To: "Baptiste Lepilleur" <gai...@fr...>;
<cpp...@li...>
Sent: Tuesday, April 23, 2002 12:23 AM
Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET



Hi,

I did a cvs update of cppunit and I can't get the testplugin to work for my
own project. Everything compiles fine inside the examples .dsw. I can run
them, life is good.

I've defined CPPUNIT_DLL. Then, I added a cppunitplugin.cpp file with the
following content

 #include <cppunit/plugin/TestPlugIn.h>

 CPPUNIT_PLUGIN_IMPLEMENT();

 // needed for an ATL project
 // note that cppunit fails if stdafx.h is included before the macro.
 #include "stdafx.h"


Finally, I link with cppunitd_dll.lib. It compiles... but it returns

Failed to load test plug-in:
Symbol [cppunitTestPlugIn] not found in dynamic libary:Bob.dll


This is really weird as simple_plugin works like a charm and I can't see
what the missing option could be.

Please help

Phil







_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel

Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem

[Baptiste L. <gai...@fr...>]

I don't have a clue on how to do that (I know barely enough to update the
automake/autoconf stuffs for each release).

A tempory fix that might work would be to edit
src/DllPlugInTester/makefile.am and
add your flag to:
DllPlugInTesterTest_LDFLAGS = -ldl

What is that '-z now' option supposed to do ? This might bring some light
about the source of the problem.

Baptiste.

----- Original Message -----
From: "Stanley Sutton" <su...@t-...>
To: "Baptiste Lepilleur" <gai...@fr...>;
<cpp...@li...>
Sent: Monday, April 22, 2002 9:37 PM
Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem



Here's the latest problem:

gmake[2]: Entering directory
`/space/local_users/sutton/projects/cppunit/src/DllPlugInTester'
/bin/bash ../../libtool --mode=link CC  -g  -o DllPlugInTester -ldl
DllPlugInTester.o CommandLineParser.o ../../src/cppunit/libcppunit.la
CC -g -o .libs/DllPlugInTester DllPlugInTester.o CommandLineParser.o  -ldl
../../src/cppunit/.libs/libcppunit.so -R/home/sutton/solaris/lib
ild: (undefined symbol) unsigned
std::deque<CppUnit::TestFailure*,std::allocator<CppUnit::TestFailure*>
>::__buffer_size() -- referenced in ../../src/cppunit/.libs/libcppunit.so
ild: (undefined symbol)
std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*> >::iterator
std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*>
>::erase(std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*>
>::iterator,std::deque<CppUnit::Test*,std::allocator<CppUnit::Test*>
>::iterator) -- referenced in ../../src/cppunit/.libs/libcppunit.so
(plus many, many more in the same vein)

As near as I can figure, the problem is in the template instantation.  I
know we've had problems with that in our code before, do to a compiler inker
bug.  We use the linker option "-z now" on all of our Solaris compiles, as
well as absolute disk paths rather than relative ones to keep from confusing
the compiler/linker.  However, I haven't been able to figure out how to add
the "-z now" to the linker.
 ".configure --prefix-/space/local_users/sutton/solaris LD_FLAGS='-z now'"
didn't seem to have any affect.



-----Original Message-----

From: Baptiste Lepilleur [mailto:gai...@fr...]

Sent: Mon 22-Apr-02 11:24

To: Stanley Sutton; cpp...@li...

Cc:

Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem


Did you follow the step indicated in Readme.CVS (and if those don't work,

did you try the lastest tar ball ?):



* Unix:



To generate the configure script, you need several auxiliary

tools.  The version numbers are minimal: later versions should

also work.



 autoconf 2.50

 - see http://www.gnu.org/directory/autoconf.html



 automake 1.4

 - see http://www.gnu.org/directory/automake.html



 libtool 1.4

 - see http://www.gnu.org/directory/libtool.html





After checking the sources out from CVS, you need to run the script



 sh autogen.sh



from the top-level source directory (i.e. the one containing this

file).  This needs only to be done once.



Baptiste.



----- Original Message -----

From: "Stanley Sutton" <su...@t-...>

To: "Baptiste Lepilleur" <gai...@fr...>;

<cpp...@li...>

Sent: Monday, April 22, 2002 5:36 PM

Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem







I'm still having some problmes on Solaris 8, using the Forte 6 compiler.  I

removed all my local files and got a fresh CVS snapshot.  Here's there first

error:



cd . && autoconf

autoconf: warning: both `configure.ac' and `configure.in' are present.

autoconf: warning: proceeding with `configure.ac'.



configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see

section `AC_LIBOBJ vs. LIBOBJS'



I'm using GNU make, by the way, as well as the GNU versions of most of the

utilities.







-----Original Message-----



From: Baptiste Lepilleur [mailto:gai...@fr...]



Sent: Sun 21-Apr-02 08:28



To: cpp...@li...



Cc:



Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball





    New snapshot. The problem on Unix should be fixed. Thanks to all those



who helped !







       KNOWN PROBLEMS:



- TestPlugIn project has not been removed from the Examples workspace (just



click cancel)



- Money example is missing dependency with cppunit.dsp







    As usal, the snapshop can be found at:







http://cppunit.sourceforge.net/snapshot/



http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz



http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz







 New in CppUnit 1.9.6:



 ----------------------







 - DllPlugInTester can be parametrized from command line



 - Two test listener plug-in examples



 - An 'hello world' example & getting started document : Money



 - Contribution: generic makefile for Borland 5.5 free compiler.



 - Bug fixes







* DllPlugInTester:







 - Advanced command line to support miscellaneous listener outputer.



   Parameters can now be passed to test plug-in:







  -c --compiler



   Use CompilerOutputter



  -x --xml [filename]



   Use XmlOutputter (if filename is omitted, then output to cout or



   cerr.



  -s --xsl stylesheet



   XML style sheet for XML Outputter



  -e --encoding encoding



   XML file encoding (UTF8, shift_jis, ISO-8859-1...)



  -b --brief-progress



   Use BriefTestProgressListener (default is TextTestProgressListener)



  -n --no-progress



   Show no test progress (disable default TextTestProgressListener)



  -t --text



   Use TextOutputter



  -o --cout



   Ouputters output to cout instead of the default cerr.



  filename[="options"]



   Many filenames can be specified. They are the name of the



   test plug-ins to load. Optional plug-ins parameters can be



   specified after the filename by adding '='.



  [:testpath]



   Optional. Only one test path can be specified. It must



   be prefixed with ':'. See TestPath constructor for syntax.







  'parameters' (test plug-in or XML filename, test path...) may contains



  spaces if double quoted. Quote may be escaped with \".







  Some examples of command lines:



DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll



CppUnitTestPlugInd.dll



  Will load 2 tests plug-ins (available in lib/), use the brief test



  progress, output the result in XML in file tests.xml and also



  output the result using the compiler outputter.







DllPlugInTesterd_dll.exe ClockerPlugInd.dll="flat" -n CppUnitTestPlugInd.dll



  Will load the 2 test plug-ins, and pass the parameter string "flat"



  to the Clocker plug-in, disable test progress. Clocker being a test



  listener plug-ins (it doesn't implements any tests, it just register



  a TestListener), this is equivalent to say 'run all the test



  of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'.







DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core



  Will run the test named "Core" (a suite in the present case ) of the



  test plug-in.







* Documentation







 - New getting started documentation. Not completed yet, but probably



   a good complement to the current cookbook. Explore the creation



   of the Money example.







* Examples







 - Money (examples/Money): the 'hello world' example. Unit tests for



   a simple Money class.







 - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp):



   unit tests for CommandLineParser. Not really an example, but only



   slightly more complex than Money.







 - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in



   that track tests and test suites running time. Parameter: "flat"



   for a reporting with a flattened tree.







 - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that



   dump the test tree as it run. Paramater: "flat" for a reporting



   with a flattened tree.







 - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp):



   CppUnit's test suite as a test plug-in.







* Contribution







  - Contributed by project cuppa team



(http://sourceforge.jp/projects/cuppa/):







 - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not



   depend on a specific CppUnit version.







* Compatiblity breaks







 - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester



   command line.







* Bug Fix:







 - DynamicLibaryManager did not report the library name when loading a



   a library.







 - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki



   ('cuppa' project team).







 - Broken build on Unix should be fixed for most (thanks to



   Jeffrey Morgan).







    Enjoy,



    Baptiste.



---



Baptiste Lepilleur <gai...@fr...>



http://gaiacrtn.free.fr/











_______________________________________________



Cppunit-devel mailing list



Cpp...@li...



https://lists.sourceforge.net/lists/listinfo/cppunit-devel

Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem

[Baptiste L. <gai...@fr...>]

Did you use ./autogen.sh too ? It does some stuff with aclocal.

To fix that bug, remove the trailing ',' at the end of the enum.

Baptiste.

----- Original Message -----
From: "Stanley Sutton" <su...@t-...>
To: "Baptiste Lepilleur" <gai...@fr...>;
<cpp...@li...>
Sent: Monday, April 22, 2002 7:38 PM
Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem



Yes, I'm up to date on the tools, although since I don't have root access on
my workstation, I use the --prefix on configure.  Starting over from scratch
fixed that particular problem.  Once again, I'm getting:

CC -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include -I../../include -g
 -Wp,-MD,.deps/DynamicLibraryManager.pp -c
DynamicLibraryManager.cpp  -KPIC -DPIC
CC: Warning: Option -Wp,-MD,.deps/DynamicLibraryManager.pp passed to ld, if
ld is invoked, ignored otherwise
"../../include/cppunit/plugin/DynamicLibraryManagerException.h", line 28:
Error: Identifier expected instead of "}".
1 Error(s) detected.

This is due to the enum in the include file, which ends in a ",}", which the
Solaris compiler treats as an error.  Also, the "-Wp,-MD,.deps/..." doesn't
seem to mean anything to the Solaris compiler, so the cp and the tr both
fail.  If the purpose of the option is to generat dependancies, the -xM
generates a dependancy list to stdout, -xM1 generates a unique list with the
/usr/include files filtered out.



-----Original Message-----

From: Baptiste Lepilleur [mailto:gai...@fr...]

Sent: Mon 22-Apr-02 11:24

To: Stanley Sutton; cpp...@li...

Cc:

Subject: Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem


Did you follow the step indicated in Readme.CVS (and if those don't work,

did you try the lastest tar ball ?):



* Unix:



To generate the configure script, you need several auxiliary

tools.  The version numbers are minimal: later versions should

also work.



 autoconf 2.50

 - see http://www.gnu.org/directory/autoconf.html



 automake 1.4

 - see http://www.gnu.org/directory/automake.html



 libtool 1.4

 - see http://www.gnu.org/directory/libtool.html





After checking the sources out from CVS, you need to run the script



 sh autogen.sh



from the top-level source directory (i.e. the one containing this

file).  This needs only to be done once.



Baptiste.



----- Original Message -----

From: "Stanley Sutton" <su...@t-...>

To: "Baptiste Lepilleur" <gai...@fr...>;

<cpp...@li...>

Sent: Monday, April 22, 2002 5:36 PM

Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem







I'm still having some problmes on Solaris 8, using the Forte 6 compiler.  I

removed all my local files and got a fresh CVS snapshot.  Here's there first

error:



cd . && autoconf

autoconf: warning: both `configure.ac' and `configure.in' are present.

autoconf: warning: proceeding with `configure.ac'.



configure.ac:37: error: do not use LIBOBJS directly, use AC_LIBOBJ (see

section `AC_LIBOBJ vs. LIBOBJS'



I'm using GNU make, by the way, as well as the GNU versions of most of the

utilities.







-----Original Message-----



From: Baptiste Lepilleur [mailto:gai...@fr...]



Sent: Sun 21-Apr-02 08:28



To: cpp...@li...



Cc:



Subject: [Cppunit-devel] CppUnit 1.9.6 tar ball





    New snapshot. The problem on Unix should be fixed. Thanks to all those



who helped !







       KNOWN PROBLEMS:



- TestPlugIn project has not been removed from the Examples workspace (just



click cancel)



- Money example is missing dependency with cppunit.dsp







    As usal, the snapshop can be found at:







http://cppunit.sourceforge.net/snapshot/



http://cppunit.sourceforge.net/snapshot/cppunit-1.9.6.tar.gz



http://cppunit.sourceforge.net/snapshot/cppunit-docs-1.9.6.tar.gz







 New in CppUnit 1.9.6:



 ----------------------







 - DllPlugInTester can be parametrized from command line



 - Two test listener plug-in examples



 - An 'hello world' example & getting started document : Money



 - Contribution: generic makefile for Borland 5.5 free compiler.



 - Bug fixes







* DllPlugInTester:







 - Advanced command line to support miscellaneous listener outputer.



   Parameters can now be passed to test plug-in:







  -c --compiler



   Use CompilerOutputter



  -x --xml [filename]



   Use XmlOutputter (if filename is omitted, then output to cout or



   cerr.



  -s --xsl stylesheet



   XML style sheet for XML Outputter



  -e --encoding encoding



   XML file encoding (UTF8, shift_jis, ISO-8859-1...)



  -b --brief-progress



   Use BriefTestProgressListener (default is TextTestProgressListener)



  -n --no-progress



   Show no test progress (disable default TextTestProgressListener)



  -t --text



   Use TextOutputter



  -o --cout



   Ouputters output to cout instead of the default cerr.



  filename[="options"]



   Many filenames can be specified. They are the name of the



   test plug-ins to load. Optional plug-ins parameters can be



   specified after the filename by adding '='.



  [:testpath]



   Optional. Only one test path can be specified. It must



   be prefixed with ':'. See TestPath constructor for syntax.







  'parameters' (test plug-in or XML filename, test path...) may contains



  spaces if double quoted. Quote may be escaped with \".







  Some examples of command lines:



DllPlugInTesterd_dll.exe -b -x tests.xml -c simple_plugind.dll



CppUnitTestPlugInd.dll



  Will load 2 tests plug-ins (available in lib/), use the brief test



  progress, output the result in XML in file tests.xml and also



  output the result using the compiler outputter.







DllPlugInTesterd_dll.exe ClockerPlugInd.dll="flat" -n CppUnitTestPlugInd.dll



  Will load the 2 test plug-ins, and pass the parameter string "flat"



  to the Clocker plug-in, disable test progress. Clocker being a test



  listener plug-ins (it doesn't implements any tests, it just register



  a TestListener), this is equivalent to say 'run all the test



  of CppUnitTestPlugIn and use ClockerPlugIn as a TestLisener'.







DllPlugInTesterd_dll.exe CppUnitTestPlugInd.dll :Core



  Will run the test named "Core" (a suite in the present case ) of the



  test plug-in.







* Documentation







 - New getting started documentation. Not completed yet, but probably



   a good complement to the current cookbook. Explore the creation



   of the Money example.







* Examples







 - Money (examples/Money): the 'hello world' example. Unit tests for



   a simple Money class.







 - DllPlugInTesterTest (src/DllPlugInTester/DllPlugInTester.dsp):



   unit tests for CommandLineParser. Not really an example, but only



   slightly more complex than Money.







 - ClockerPlugIn (examples/ClockerPlugIn): a test listener plug-in



   that track tests and test suites running time. Parameter: "flat"



   for a reporting with a flattened tree.







 - DumperPlugIn (examples/DumperPlugIn): a test listener plug-in that



   dump the test tree as it run. Paramater: "flat" for a reporting



   with a flattened tree.







 - CppUnitTestPlugIn (examples/cppunitest/CppUnitTestPlugIn.dsp):



   CppUnit's test suite as a test plug-in.







* Contribution







  - Contributed by project cuppa team



(http://sourceforge.jp/projects/cuppa/):







 - Makefile for CppUnit with Borland C++ 5.5 free compiler: does not



   depend on a specific CppUnit version.







* Compatiblity breaks







 - DllPlugInTester: (1.9.4 only), should add -c to DllPlugInTester



   command line.







* Bug Fix:







 - DynamicLibaryManager did not report the library name when loading a



   a library.







 - BeosDynamicLibraryManager: fixed thanks to Shibu Yoshiki



   ('cuppa' project team).







 - Broken build on Unix should be fixed for most (thanks to



   Jeffrey Morgan).







    Enjoy,



    Baptiste.



---



Baptiste Lepilleur <gai...@fr...>



http://gaiacrtn.free.fr/











_______________________________________________



Cppunit-devel mailing list



Cpp...@li...



https://lists.sourceforge.net/lists/listinfo/cppunit-devel

RE: [Cppunit-devel] Some Questions

[Michel A. <Arm...@si...>]

> > 1. CppUnit::Test
> > Why are the find-related methods not const? Shouldn't they? 
> I feel const
> > find-methods are somewhat more intuitive, aren't they?
> 
> They all store the test in a TestPath, which store non const 
> pointer on the
> traversed test, or returns a non const pointer on a test. 
> Since TestPath is
> mainly used to run test (non const) method, it makes sense (at least I
> beleive so). Let's me know if you have another point of view 
> on the suggest.
> At first I wanted those methods to be const too.

I'd suggest, to make the find() methods const anyway. I'd also leave the
returned information non-const. This of course makes it neccessary to
const_cast the returned information (pointer to Tests etc.). In this case I
think a const_cast is acceptable, because the find-methods themselves do not
modify the Tests; just subsequent calls on the result of the find-methods
may modify the Tests.
Any other opinions around here?

> 
> >
> > 2. CppUnit::TestDecorator
> > This class doesn't delegate _all_ the methods. IMHO, in 
> order to have a
> > completely transparent Decorator, it really should delegate 
> all methods.
> > What do you think of this?
> 
> I guess that makes sense. At the current time, it delegates 
> all the virtual
> pure method. Though I haven't found much use for that class 
> yet (I used it
> for the first time in the first 'writing' of DllPlugInTester 
> were I need to
> pass Test to the TestRunner without them being destroyed 
> after the run).
> 
> > 3. CppUnit::TestCase
> > Maybe we can enhance the run() method, so that it can also 
> properly (with
> > SourceLine information) catch failures in both setUp() and 
> tearDown()?
> 
> To you means catching possible assertions made in 
> setUp()/tearDown() ? We
> don't have the SourceLine information for other exception.

This is exactly what I meant. Setup() and tearDown() methods may also
contain code which may not execute as expected. To be able to insert some
CPPUNIT_ASSERTs there would certainly help a lot.

> 
> >
> > 4. CppUnit::TestSuite
> > There is an unused m_name in this class 
> (CppUnit::TestComposite already
> > defines this member; and actually uses it ;-)). Let's 
> remove that unused
> > member?
> Removed it. Left over of when I pulled up those into TestComposite.
> 
> > 5. CppUnit::TestRunner
> > Neither CppUnit::TextUi::TestRunner nor the MFC-based 
> TestRunner reuses
> the
> > generic TestRunner in some way. Is that intended? Or are there some
> > refactorings pending? Just wondering...
> TextUi can be derived from CppUnit::TestRunner (only some 
> default listener
> and outputter are added). The Mfc TestRunner could be derived 
> too, it use a
> similar 'test' suite management for added test, but the run() 
> method does
> not have anything in comon (does not take a TestResult, or a 
> test path)?
> Plus the test can be run many times... I don't really know 
> what to do with
> that one.

> 
> > I could do (2.) - (4.) my own and submit the changes; I 
> just don't know
> how
> > to best submit these changes. (I don't have cvs-access here :-(.)
> 
> Fixed. You should have CVS access now.

No, its more a problem of being behind a nasty firewall... :-(

Armin.

[Cppunit-devel] How to use clocker in my own project ?

[Philippe L. <phi...@ca...>]

Hi guys,

Now that I've managed to figure out how to do a proper copy from one =
place to the other :) I'm ready to incorporate cppunit results inside =
the build process (I'm using ant to do the builds).=20

I'd prefer to have the xml output with the test duration times included. =
I want to have the default XML output from DllPluginTester to also have =
timing values. What is the best way to achieve this ?=20

I think I might be missing some basic concepts on how I can mix and =
match the different listener and outputer. I'm pretty sure I should look =
at the ClockPlugIn for guidance.

I did the following naive test hoping that some magic would occur

DllPlugInTesterd_dll -x test.xml -c Mine.dll clockerplugind.dll
.
(0.050s) All Tests
   +--(0.050s) InputErrorTest
   |  +--(0.050s) InputErrorTest.testNormalUsage

Total elapsed time: (0.050s) , average test case time: (0.150s) OK (1)

The command line output is indeed magic :) (although there is a bug in =
the average test case time). However, the XML output is as follows.


<?xml version=3D"1.0" encoding=3D'' standalone=3D'yes' ?>
<TestRun>
  <FailedTests></FailedTests>
  <SuccessfulTests>
    <Test id=3D"1">
      <Name>InputErrorTest.testNormalUsage</Name>
    </Test>
  </SuccessfulTests>
  <Statistics>
    <Tests>1</Tests>
    <FailuresTotal>0</FailuresTotal>
    <Errors>0</Errors>
    <Failures>0</Failures>
  </Statistics>
</TestRun>

Please let me know if you know in which direction I should go to add a =
time attribute to the Test results. Thanks.


Phil

Re: [Cppunit-devel] CppUnit 1.9.6 tar ball - Solaris problem

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

On Mon, Apr 22, 2002 at 12:38:25PM -0500, Stanley Sutton wrote:

> Also, the "-Wp,-MD,.deps/..." doesn't
> seem to mean anything to the Solaris compiler, so the cp and the tr both fail. 
> If the purpose of the option is to generat dependancies, the -xM generates a
> dependancy list to stdout, -xM1 generates a unique list with the /usr/include
> files filtered out.

Yes, that is the dependency-generating stuff from automake.

I can't quickly find a list of compilers that automake supports, but it
sounds like yours is not one of them.  The automake team would probably
like to know how to enable it for your compiler; send them email at
<bug...@gn...>.

In the meantime, automake supports a --disable-dependency-tracking
that you can use.  This may not be supported in automake versions
prior to 1.5.



On Mon, Apr 22, 2002 at 02:37:42PM -0500, Stanley Sutton wrote:

> As near as I can figure, the problem is in the template instantation.  I know
> we've had problems with that in our code before, do to a compiler inker bug. 
> We use the linker option "-z now" on all of our Solaris compiles, as well as
> absolute disk paths rather than relative ones to keep from confusing the
> compiler/linker.  However, I haven't been able to figure out how to add the "-z
> now" to the linker.  ".configure --prefix-/space/local_users/sutton/solaris
> LD_FLAGS='-z now'" didn't seem to have any affect.

The variable is "LDFLAGS".  

Setting it at configure time should work with autoconf 2.5x, I
believe.  If it doesn't, you can always set it on the "make" command
line.




-- 
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] CppUnit 1.9.6 tar ball -- Visual .NET

[Philippe L. <phi...@ca...>]

Never mind... I had a bad version of the Include files...=20

Sigh... spent the whole afternoon on this... Stupid copy doesn't work =
when the file is in use... Stupid stupid stupid.


Phil

> -----Original Message-----
> From: Philippe Lavoie=20
> Sent: Monday, April 22, 2002 6:24 PM
> To: Baptiste Lepilleur; cpp...@li...
> Subject: RE: [Cppunit-devel] CppUnit 1.9.6 tar ball -- Visual .NET
>=20
>=20
>=20
> Hi,
>=20
> I did a cvs update of cppunit and I can't get the testplugin=20
> to work for my own project. Everything compiles fine inside=20
> the examples .dsw. I can run them, life is good.
>=20
> I've defined CPPUNIT_DLL. Then, I added a cppunitplugin.cpp=20
> file with the following content
>=20
>  #include <cppunit/plugin/TestPlugIn.h>
>=20
>  CPPUNIT_PLUGIN_IMPLEMENT();
>=20
>  // needed for an ATL project
>  // note that cppunit fails if stdafx.h is included before the macro.
>  #include "stdafx.h" =20
>=20
>=20
> Finally, I link with cppunitd_dll.lib. It compiles... but it returns
>=20
> Failed to load test plug-in:
> Symbol [cppunitTestPlugIn] not found in dynamic libary:Bob.dll
>=20
>=20
> This is really weird as simple_plugin works like a charm and=20
> I can't see what the missing option could be.
>=20
> Please help
>=20
> Phil
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Cppunit-devel mailing list
> Cpp...@li...
> https://lists.sourceforge.net/lists/listinfo/cppunit-devel
>=20