cppunit-devel Mailing List for CppUnit - C++ port of JUnit (Page 51)
Brought to you by:
blep
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
(21) |
May
(96) |
Jun
(109) |
Jul
(42) |
Aug
(6) |
Sep
(106) |
Oct
(60) |
Nov
(20) |
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(7) |
Feb
(11) |
Mar
(49) |
Apr
(124) |
May
(30) |
Jun
(37) |
Jul
(53) |
Aug
(33) |
Sep
(21) |
Oct
(22) |
Nov
(19) |
Dec
(15) |
| 2003 |
Jan
(34) |
Feb
(25) |
Mar
(11) |
Apr
(12) |
May
(16) |
Jun
(24) |
Jul
(23) |
Aug
(23) |
Sep
(42) |
Oct
(7) |
Nov
(32) |
Dec
(33) |
| 2004 |
Jan
(41) |
Feb
(41) |
Mar
(24) |
Apr
(25) |
May
(18) |
Jun
(13) |
Jul
(11) |
Aug
(15) |
Sep
(22) |
Oct
(10) |
Nov
(15) |
Dec
(9) |
| 2005 |
Jan
(4) |
Feb
(15) |
Mar
(11) |
Apr
(16) |
May
(29) |
Jun
(17) |
Jul
(27) |
Aug
(12) |
Sep
(9) |
Oct
(10) |
Nov
(5) |
Dec
(6) |
| 2006 |
Jan
(2) |
Feb
(6) |
Mar
(7) |
Apr
(2) |
May
(1) |
Jun
(5) |
Jul
(8) |
Aug
(6) |
Sep
(10) |
Oct
(11) |
Nov
(15) |
Dec
(2) |
| 2007 |
Jan
(12) |
Feb
(22) |
Mar
(10) |
Apr
(7) |
May
(1) |
Jun
(8) |
Jul
(4) |
Aug
(1) |
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(7) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
|
| 2010 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Baptiste L. <bl...@cl...> - 2001-09-21 19:15:51
|
Finally heard from Patrick Berny. He fixed the problem (some part of the
registry was not updated).
The fix has been comitted. Refer to INSTALL-WIN32.txt for install
instruction. This is really a nifty feature. Thanks again Patrick!
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).
|
|
From: Baptiste L. <gai...@fr...> - 2001-09-21 10:43:23
|
Quoting "Steve M. Robbins" <ste...@vi...>: > Hello, > > Would anyone get offended if we call the next release "1.6.0", and > move to the convention that version x.y.z comes from the STABLE branch > for even-valued "y", and from the UNSTABLE branch for odd-valued "y" ? I'm not really familiar with Linux version numbering. Let me check a few fact: - z is a "patch level": nothing changed in functionnality, but some bug where fixed. - y is a "functionnality/compatibility level": some functionnality where added, or some minor compability issues where raised. - x is an "architecture level": major architecture change, functionnality ? Anyway, a lot of functionnality have been added since the last release. So 1.6.0 sound right. Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html Language: English, French |
|
From: Bastiaan B. <Bas...@li...> - 2001-09-21 08:39:51
|
> -----Oorspronkelijk bericht----- > Van: Steve M. Robbins [mailto:ste...@vi...] > Verzonden: Thursday, September 20, 2001 9:27 PM > Aan: CppUnit Development > Onderwerp: [Cppunit-devel] version 1.6? >=20 >=20 > Hello, >=20 > Would anyone get offended if we call the next release "1.6.0", and > move to the convention that version x.y.z comes from the STABLE branch > for even-valued "y", and from the UNSTABLE branch for odd-valued "y" ? >=20 Sounds like a good idea. I'd say, go for it.=20 Also, since Micheal Feather's 1.5 version enough things have changed to justify an increment of y. Good luck, Bastiaan |
|
From: Steve M. R. <ste...@vi...> - 2001-09-20 19:26:37
|
Hello, Would anyone get offended if we call the next release "1.6.0", and move to the convention that version x.y.z comes from the STABLE branch for even-valued "y", and from the UNSTABLE branch for odd-valued "y" ? -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 |
|
From: Steve M. R. <ste...@vi...> - 2001-09-20 15:47:55
|
Hi, On Thu, Sep 20, 2001 at 05:34:09PM +0200, Volker Boerchers wrote: > there seems to be a problem on Linux/gcc version 2.95.2: > > g++ -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include -I../../include > -O2 -c TestAssert.cpp -Wp,-MD,.deps/TestAssert.TPlo -fPIC -DPIC -o > .libs/TestAssert.o > In file included from ../../include/cppunit/TestAssert.h:5, > from TestAssert.cpp:7: > ../../include/cppunit/Portability.h:67: #error Cannot define > CppUnit::OStringStream. > make[2]: *** [TestAssert.lo] Error 1 > make[2]: Leaving directory > `/home/vboerchers/billing/cppunit-2001-09-20/src/cppunit' Grr. Do you have any of the following headers: sstream, sstream.h, strstream, or strstream.h? Can you please send me the file "config.log" for this build? Thanks. -- 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 |
|
From: Patrick H. <pa...@13...> - 2001-09-20 15:47:25
|
Steve, I must have botched something, because I got it working now without changing Portability.h. For the record, we're using MIPSpro version 7.3.1.2m which is the latest from SGI. Thanks for your help. -Patrick "Steve M. Robbins" <ste...@vi...> wrote: } On Wed, Sep 19, 2001 at 09:30:57AM -0500, Patrick Hartling wrote: } > We have been compiling with -LANG:std on IRIX. Most of our projects use } > that option to ensure standards-compliant C++ with MIPSpro. I just did a } > build of our test suite against the latest CppUnit code, and it is still } > failing. } } Odd. When I use -LANG:std, the configure script detects and uses the } "sstream" code, rather than "strstream". However, "CC -version" says } "MIPSpro Compilers: Version 7.30" here; is that newwer than yours? } } Do you have /usr/include/CC/sstream? } If so, can you check and/or send to me config.log and config/config.h, please *** . } } } > Using strstream instead of strstream.h fixes the problem. I } > haven't tested the effects of this change on platforms besides IRIX and } > Linux, so I cannot be sure that this change would not break portability } > elsewhere. } } I fear it may weaken portability. If necessary, I will improve the } configure script so that it checks for both <strstream> and } <strstream.h>. I'd like to first verify that you have no <sstream>, } though. } } Thanks for your quick (re-)test! } } -Steve } } } > } So I closed the bug report. } > } (Did you get an email notice?) } } Did you? I'm new to the sourceforge bug system, so I'd like to } know whether bug submitters ever get any feedback. } } -- } 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 } Patrick L. Hartling | Research Assistant, VRAC pa...@13... | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ |
|
From: Volker B. <boe...@we...> - 2001-09-20 15:34:54
|
On Thu, 20 Sep 2001, Steve M. Robbins wrote: > Hi, > > I made a new snapshot, available at location > > http://www.bic.mni.mcgill.ca/~stever/Software/cppunit-2001-09-20.tar.gz > > Changes from yesterday include > > * configure script will probe for <strstream> > * TestSetupTest restored to CppUnit unit test > * tweaking of MS VC++ build there seems to be a problem on Linux/gcc version 2.95.2: g++ -DHAVE_CONFIG_H -I. -I. -I../../config -I../../include -I../../include -O2 -c TestAssert.cpp -Wp,-MD,.deps/TestAssert.TPlo -fPIC -DPIC -o .libs/TestAssert.o In file included from ../../include/cppunit/TestAssert.h:5, from TestAssert.cpp:7: ../../include/cppunit/Portability.h:67: #error Cannot define CppUnit::OStringStream. make[2]: *** [TestAssert.lo] Error 1 make[2]: Leaving directory `/home/vboerchers/billing/cppunit-2001-09-20/src/cppunit' Regards, Volker -- Volker Boerchers, boe...@we... |
|
From: Baptiste L. <gai...@fr...> - 2001-09-20 15:26:14
|
Quoting "Summerwill, Bob" <BSu...@eu...>: > > There's still the warning when compiling DSPlugIn ... > > > --------------------Configuration: DSPlugIn - Win32 > Debug-------------------- > Creating Type Library... > Microsoft (R) MIDL Compiler Version 5.01.0164 > > [ chopped most of the build output ] > > DSAddIn.cpp > DSPlugIn.cpp > TestRunnerDSPlugin_i.c > Linking... > Creating library Debug/TestRunnerDSPlugInD.lib and object > Debug/TestRunnerDSPlugInD.exp > TestRunnerDSPlugInD.exp : warning LNK4070: /OUT:TestRunnerDSPlugin.dll > directive in .EXP differs from output filename > "../../../lib/TestRunnerDSPlugInD.dll"; ignoring directive > Performing Registration > Server registration done! > > TestRunnerDSPlugInD.dll - 0 error(s), 1 warning(s) I'm not sure how to get ride of that one. I think it's related to the .def file. Note that the registration has been disabled (I commented out the command that tried to execute the DLL). I posted a mail to Patrick to ask him how to fix that (I'm not sure how add-ins are supposed to be registered, but the DllRegisterServer function is not exported, meaning that regsvr32 can not be used to register the COM component). > And the exception::operator() unit test still fails. Excerpt from INSTALL-WIN32.txt FAQ ;-) : 3) Why does the test ExceptionTest.testAssignment failed in CppUnit test suite ? I've never been able to figure out why that test fails. It seems to be specific to VC++ since the test passes with gcc. If you can figure out the failure, please let us know! > > Apart from that it seems to work OK. So we can say that on the windows side it's a go! > > Are you going to remove the non-"Example.dsw" DSWs before the release? No, after. Things are finally working, I'd rather wait before changing things around again. Thanks Bob, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html Language: English, French |
|
From: Summerwill, B. <BSu...@eu...> - 2001-09-20 12:56:26
|
There's still the warning when compiling DSPlugIn ... --------------------Configuration: DSPlugIn - Win32 Debug-------------------- Creating Type Library... Microsoft (R) MIDL Compiler Version 5.01.0164 [ chopped most of the build output ] DSAddIn.cpp DSPlugIn.cpp TestRunnerDSPlugin_i.c Linking... Creating library Debug/TestRunnerDSPlugInD.lib and object Debug/TestRunnerDSPlugInD.exp TestRunnerDSPlugInD.exp : warning LNK4070: /OUT:TestRunnerDSPlugin.dll directive in .EXP differs from output filename "../../../lib/TestRunnerDSPlugInD.dll"; ignoring directive Performing Registration Server registration done! TestRunnerDSPlugInD.dll - 0 error(s), 1 warning(s) And the exception::operator() unit test still fails. Apart from that it seems to work OK. Are you going to remove the non-"Example.dsw" DSWs before the release? Cheers, Bob -----Original Message----- From: Baptiste Lepilleur [mailto:gai...@fr...] Sent: 20 September 2001 13:02 To: cpp...@li... Subject: Re: [Cppunit-devel] Snapshot for 2001-09-20 Quoting "Steve M. Robbins" <ste...@vi...>: > Hi, > > I made a new snapshot, available at location > > > http://www.bic.mni.mcgill.ca/~stever/Software/cppunit-2001-09-20.tar.gz > > Changes from yesterday include > > * configure script will probe for <strstream> > * TestSetupTest restored to CppUnit unit test > * tweaking of MS VC++ build Everything seems to be working fine for me. So it is a go! Has anybody else tested this snapshot on Windows ? Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html Language: English, French _______________________________________________ Cppunit-devel mailing list Cpp...@li... https://lists.sourceforge.net/lists/listinfo/cppunit-devel |
|
From: Baptiste L. <gai...@fr...> - 2001-09-20 12:02:12
|
Quoting "Steve M. Robbins" <ste...@vi...>: > Hi, > > I made a new snapshot, available at location > > > http://www.bic.mni.mcgill.ca/~stever/Software/cppunit-2001-09-20.tar.gz > > Changes from yesterday include > > * configure script will probe for <strstream> > * TestSetupTest restored to CppUnit unit test > * tweaking of MS VC++ build Everything seems to be working fine for me. So it is a go! Has anybody else tested this snapshot on Windows ? Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html Language: English, French |
|
From: Steve M. R. <ste...@vi...> - 2001-09-20 04:32:41
|
Hi, I made a new snapshot, available at location http://www.bic.mni.mcgill.ca/~stever/Software/cppunit-2001-09-20.tar.gz Changes from yesterday include * configure script will probe for <strstream> * TestSetupTest restored to CppUnit unit test * tweaking of MS VC++ build -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 |
|
From: Baptiste L. <bl...@cl...> - 2001-09-19 20:14:20
|
> > } So I closed the bug report.
> > } (Did you get an email notice?)
>
> Did you? I'm new to the sourceforge bug system, so I'd like to
> know whether bug submitters ever get any feedback.
You need to subscribe on the bug page to say "I want to receive an
e-mail when the status change" (if I remember correctly).
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).
|
|
From: Steve M. R. <ste...@vi...> - 2001-09-19 14:51:52
|
On Wed, Sep 19, 2001 at 09:30:57AM -0500, Patrick Hartling wrote: > We have been compiling with -LANG:std on IRIX. Most of our projects use > that option to ensure standards-compliant C++ with MIPSpro. I just did a > build of our test suite against the latest CppUnit code, and it is still > failing. Odd. When I use -LANG:std, the configure script detects and uses the "sstream" code, rather than "strstream". However, "CC -version" says "MIPSpro Compilers: Version 7.30" here; is that newwer than yours? Do you have /usr/include/CC/sstream? If so, can you check and/or send to me config.log and config/config.h, please. > Using strstream instead of strstream.h fixes the problem. I > haven't tested the effects of this change on platforms besides IRIX and > Linux, so I cannot be sure that this change would not break portability > elsewhere. I fear it may weaken portability. If necessary, I will improve the configure script so that it checks for both <strstream> and <strstream.h>. I'd like to first verify that you have no <sstream>, though. Thanks for your quick (re-)test! -Steve > } So I closed the bug report. > } (Did you get an email notice?) Did you? I'm new to the sourceforge bug system, so I'd like to know whether bug submitters ever get any feedback. -- 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 |
|
From: Patrick H. <pa...@13...> - 2001-09-19 14:31:29
|
We have been compiling with -LANG:std on IRIX. Most of our projects use that option to ensure standards-compliant C++ with MIPSpro. I just did a build of our test suite against the latest CppUnit code, and it is still failing. Using strstream instead of strstream.h fixes the problem. I haven't tested the effects of this change on platforms besides IRIX and Linux, so I cannot be sure that this change would not break portability elsewhere. -Patrick "Steve M. Robbins" <ste...@vi...> wrote: } On Thu, Aug 30, 2001 at 09:43:10AM -0500, Patrick Hartling wrote: } > A week ago, I submitted a bug report (#454711) to fix a compiler error } > in include/cppunit/Portability.h. This error occurs with SGI's MIPSpro } > Compilers 7.3.1.2 and is the mostly the result of some missing std::'s. } > The bug report contains the patch I made to get it compiling. Is there } > any chance of this patch being applied sometime soon? Thanks. } } Hello Patrick, } } I am going through the bug reports now. } } In the case of the MIPSpro compiler, what you need to do is enable the } standard library using } } ./configure CXX='CC -LANG:std' .... } } So I closed the bug report. } (Did you get an email notice?) } } -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 } } } _______________________________________________ } Cppunit-devel mailing list } Cpp...@li... } https://lists.sourceforge.net/lists/listinfo/cppunit-devel Patrick L. Hartling | Research Assistant, VRAC pa...@13... | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ |
|
From: Baptiste L. <gai...@fr...> - 2001-09-19 13:12:23
|
Quoting "Steve M. Robbins" <ste...@vi...>: > Hi, > > I went through the open bug reports and tinkered a bit with > the build process to address them. I think we're getting close > to a new release. > > Since not everyone is willing or able to use sources from CVS, I have > built a release-candidate tar package, and placed it at the following > URL: > > > http://www.bic.mni.mcgill.ca/~stever/Software/cppunit-2001-09-19.tar.gz > > [I didn't find a place on source forge for snapshots --- where should > I look?] TestSetUpTest.cpp and TestSetUpTest.h are missing in examples/cppunittests (that would account for our missing unit test). Those are not in the fakefile.am file. Other points that need fixing: - HostApp release conf.: bad library path - DSPlugIn release conf.: bad output path for the *.tlb file Sight... I swear I already fixed that yesterday. Well, I'll redo that this evening. Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html Language: English, French |
|
From: Summerwill, B. <BSu...@eu...> - 2001-09-19 08:54:22
|
I grabbed the CVS HEAD and tried building debug and release configurations
of each application. Here's what I found ....
Examples.DSW workspace
----------------------
Hierarchy and CppUnitTestMain build without any problems, in both Debug and
Release configurations.
HostApp & CppTestApp build successfully, but the custom build step for
DSPlugIn ...
"$(TargetPath)" /RegServer
echo regsvr32 exec. time > "$(OutDir)\regsvr32.trg"
echo Server registration done!
... appears to try to execute the DLL being constructed, which pops up a
dialog asking the user to choose
an application to open the DLL with. I don't know what this registration
step is for, but can only assume
that the custom build step isn't correct.
There are a number of unnecessary dependencies in this DSW. These appears
to be the actual dependencies required ...
CppUnit DSPlugIn
| |
+----------+------------+ |
| | | |
Hierarchy CppUnit TestRunner
TestMain |
+------+------+
| |
HostApp CppTestApp
So the DSW only needs ...
Hierarchy -> CppUnit
CppUnitTestMain -> CppUnit
TestRunner -> CppUnit
TestRunner -> DSPlugIn
HostApp -> TestRunner
CppTestApp -> TestRunner.
I've got a few questions / suggestions too.
There appear to be a large number of workspaces, some of which contain
duplicate parts of CppUnit. One example of this is the Hierarchy workspace,
which contains just the Hierarchy application. This application is also
available in the Examples.dsw workspace. In my experience, it always works
better if you have all the applications in a single workspace (like
Examples.dsw) or in their own workspace (Hierarchy.dsw), but not both.
Having both means you've got twice the maintainance.
What is the CrossPlatform Setting configuration?
Please could someone explain what DSPlugIn, TestPlugIn, TestPlugInRunner and
TestRunner are, please?
Cheers,
Bob
--------------------Configuration: DSPlugIn - Win32
Debug--------------------
Creating Type Library...
Processing D:\cvsroot\cppunit\src\msvc6\DSPlugIn\TestRunnerDSPlugin.idl
TestRunnerDSPlugin.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\oaidl.idl
oaidl.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\objidl.idl
objidl.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\unknwn.idl
unknwn.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\wtypes.idl
wtypes.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\ocidl.idl
ocidl.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\oleidl.idl
oleidl.idl
Processing C:\Program Files\Microsoft Visual
Studio\VC98\INCLUDE\servprov.idl
servprov.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\urlmon.idl
urlmon.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\msxml.idl
msxml.idl
Compiling resources...
Compiling...
StdAfx.cpp
Compiling...
DSAddIn.cpp
DSPlugIn.cpp
TestRunnerDSPlugin_i.c
Linking...
Creating library Debug/TestRunnerDSPlugInD.lib and object
Debug/TestRunnerDSPlugInD.exp
TestRunnerDSPlugInD.exp : warning LNK4070: /OUT:TestRunnerDSPlugin.dll
directive in .EXP differs from output filename
"../../../lib/TestRunnerDSPlugInD.dll"; ignoring directive
Performing Registration
Server registration done!
-----Original Message-----
From: Baptiste Lepilleur [mailto:bl...@cl...]
Sent: 18 September 2001 20:12
To: Cpp Unit Develpment Mailing List
Subject: Re: [Cppunit-devel] Coming release (was: Is this project dead?)
----- Original Message -----
From: "Baptiste Lepilleur" <gai...@fr...>
To: "Cpp Unit Develpment Mailing List" <cpp...@li...>
Sent: Tuesday, September 18, 2001 12:42 PM
Subject: RE: [Cppunit-devel] Coming release (was: Is this project dead?)
> Quoting "Summerwill, Bob" <BSu...@eu...>:
>
> >
> > I just grabbed the CVS HEAD, and compiled it with MSVC++ 6.0. Here were
> > the
> > results ....
[...]
> In any event, I'll fix CppUnitTestApp dependecy this evening (2) ;-)
It's done. Can you or somebody else test the current CVS HEAD for
Windows ?
Thanks,
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...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel
|
|
From: Steve M. R. <ste...@vi...> - 2001-09-19 05:17:34
|
Hi, I went through the open bug reports and tinkered a bit with the build process to address them. I think we're getting close to a new release. Since not everyone is willing or able to use sources from CVS, I have built a release-candidate tar package, and placed it at the following URL: http://www.bic.mni.mcgill.ca/~stever/Software/cppunit-2001-09-19.tar.gz [I didn't find a place on source forge for snapshots --- where should I look?] I would urge all those who have submitted bug reports --- particularly those two having build problems on solaris --- to download and test out this snapshot. Thanks, -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 |
|
From: Steve M. R. <ste...@vi...> - 2001-09-19 03:39:43
|
On Thu, Aug 30, 2001 at 09:43:10AM -0500, Patrick Hartling wrote: > A week ago, I submitted a bug report (#454711) to fix a compiler error > in include/cppunit/Portability.h. This error occurs with SGI's MIPSpro > Compilers 7.3.1.2 and is the mostly the result of some missing std::'s. > The bug report contains the patch I made to get it compiling. Is there > any chance of this patch being applied sometime soon? Thanks. Hello Patrick, I am going through the bug reports now. In the case of the MIPSpro compiler, what you need to do is enable the standard library using ./configure CXX='CC -LANG:std' .... So I closed the bug report. (Did you get an email notice?) -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 |
|
From: Baptiste L. <bl...@cl...> - 2001-09-18 19:13:04
|
----- Original Message -----
From: "Baptiste Lepilleur" <gai...@fr...>
To: "Cpp Unit Develpment Mailing List" <cpp...@li...>
Sent: Tuesday, September 18, 2001 12:42 PM
Subject: RE: [Cppunit-devel] Coming release (was: Is this project dead?)
> Quoting "Summerwill, Bob" <BSu...@eu...>:
>
> >
> > I just grabbed the CVS HEAD, and compiled it with MSVC++ 6.0. Here were
> > the
> > results ....
[...]
> In any event, I'll fix CppUnitTestApp dependecy this evening (2) ;-)
It's done. Can you or somebody else test the current CVS HEAD for
Windows ?
Thanks,
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).
|
|
From: Baptiste L. <gai...@fr...> - 2001-09-18 10:43:00
|
Quoting "Summerwill, Bob" <BSu...@eu...>: > > I just grabbed the CVS HEAD, and compiled it with MSVC++ 6.0. Here were > the > results .... > > > 1. CppUnitTestApp fails to compile, in TestRunner (see below). [...] That problem is solved by compiling the TestRunner project from the TestRunner.dsw workspace (which cause DSPlugIn.dsp to be compiled and create the missing files). I have recently though about that dependency problem. With the increasing number of projects and examples, it become harder to maintain all the examples. I have come with 3 courses of actions: 1) Remove all dependency in the examples. Clearly state in INSTALL-WIN32.txt that TestRunner.dsp must be build from TestRunner.dsw before building any examples. 2) Same as 1), but keep an example which can compile 'as this' (CppUnitTestApp). 3)Maintains dependencies for all projects. I'll go for (2) unless some good arguments are submited. (3) is a lot of works and it's easy to mess up (like I just did there). (1) would be nice, but I like to be able to grab a new release and just run the sample with all the unit test right away. What do you think ? In any event, I'll fix CppUnitTestApp dependecy this evening (2) ;-) > > 2. CppUnitTestMain compiles, but the unit tests fail when run ... > > > !!!FAILURES!!! > Test Results: > Run: 85 Failures: 1 Errors: 0 > There was 1 failure: > 1) test: ExceptionTest.testAssignment line: 103 > d:\cvsroot\cppunit\examples\cppunittest\exceptiontest.cpp > expected: message > but was: Unknown exception > > > This problem appears to have been introduced when the call to > std::exception::operator=() was added to the > CppUnit::Exception::operator=() > implementation. The test code causes an unhandled exception when > exception::what() is called on the copied object. Hmm, I actually never been able to have that test pass sucessfuly (It was already failing when I wrote that test case). Never been able to figure out what was wrong :-( > > > > 3. HostApp fails to compile (failing in TestRunner again). [...] Same as 1. Thanks a lot Bob, Baptiste. --- Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html Language: English, French |
|
From: Summerwill, B. <BSu...@eu...> - 2001-09-18 09:02:47
|
I just grabbed the CVS HEAD, and compiled it with MSVC++ 6.0. Here were the
results ....
1. CppUnitTestApp fails to compile, in TestRunner (see below).
--------------------Configuration: TestRunner - Win32
Debug--------------------
Compiling resources...
Compiling...
StdAfx.cpp
Compiling...
ListCtrlFormatter.cpp
ListCtrlSetter.cpp
MsDevCallerListCtrl.cpp
D:\cvsroot\cppunit\src\msvc6\testrunner\MsDevCallerListCtrl.cpp(9) : fatal
error C1083: Cannot open include file:
'msvc6/DSPlugin/TestRunnerDSPlugin.h': No such file or directory
ProgressBar.cpp
TestRunnerApp.cpp
TestRunnerDlg.cpp
TreeHierarchyDlg.cpp
ActiveTest.cpp
GUITestResult.cpp
TestRunner.cpp
TestRunnerModel.cpp
MostRecentTests.cpp
Generating Code...
Error executing snCl.exe.
CppUnitTestApp.exe - 1 error(s), 0 warning(s)
2. CppUnitTestMain compiles, but the unit tests fail when run ...
!!!FAILURES!!!
Test Results:
Run: 85 Failures: 1 Errors: 0
There was 1 failure:
1) test: ExceptionTest.testAssignment line: 103
d:\cvsroot\cppunit\examples\cppunittest\exceptiontest.cpp
expected: message
but was: Unknown exception
This problem appears to have been introduced when the call to
std::exception::operator=() was added to the CppUnit::Exception::operator=()
implementation. The test code causes an unhandled exception when
exception::what() is called on the copied object.
3. HostApp fails to compile (failing in TestRunner again).
--------------------Configuration: TestRunner - Win32
Debug--------------------
Build : warning : failed to (or don't know how to) build
'D:\cvsroot\cppunit\include\msvc6\DSPlugIn\TestRunnerDSPlugin_i.c'
Compiling...
MsDevCallerListCtrl.cpp
D:\cvsroot\cppunit\src\msvc6\testrunner\MsDevCallerListCtrl.cpp(9) : fatal
error C1083: Cannot open include file:
'msvc6/DSPlugin/TestRunnerDSPlugin.h': No such file or directory
Error executing snCl.exe.
HostApp.exe - 1 error(s), 1 warning(s)
Cheers,
Bob
-----Original Message-----
From: Baptiste Lepilleur [mailto:bl...@cl...]
Sent: 17 September 2001 22:42
To: Cpp Unit Develpment Mailing List
Subject: Re: [Cppunit-devel] Coming release (was: Is this project dead?)
> Okay, then. For the unix side, I think everything is basically there.
> I will check that it works on IRIX and maybe freebsd if I get the
> time, but I don't anticipate changing anything other than READMEs,
> NEWS and minor release stuff.
>
> However, I know nothing about the MS windows side of things.
> Baptiste? Can you check things out and let me know whether
> anything needs fixing?
Well, I just did some major clean up in the different configurations for
all the projects in CppUnit (was somewhat a mess). That means that
everything should compile fine this time. Also added a small install guide
for VC++: INSTALL-WIN32.txt (by the way, I added it to EXTRA_DIST in
makefile.am, was that the correct things to do?). Could you also apply the
process to convert EOL to DOS format when making the dist (as is done for
*.dsw and *.dsp files)?
I like it if another VC++ user could grab the last CVS version and get a
rain check on this. For the last release it compiled fine for me, but not
everybody ! Any volunteer ?
I went trough the bug reports, and corrected somes (#448363, #448332).
Many reported bugs have already been fixed since release 1.5.5 (I'm closing
them). Has the MIPSPro patch been included ? And what about the report that
it does not compile with gcc 3.0 ?
Still haven't heard from Patrick about the DSPlugIn (can't get it to
work with VC++). But that is not a blocking issue (we just can not use that
functionnality).
I will try that version of CppUnit tomorrow at work where I have better
test suites.
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...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel
|
|
From: Steve M. R. <ste...@vi...> - 2001-09-18 03:13:54
|
On Mon, Sep 17, 2001 at 11:41:57PM +0200, Baptiste Lepilleur wrote: > > However, I know nothing about the MS windows side of things. > > Baptiste? Can you check things out and let me know whether > > anything needs fixing? > > Well, I just did some major clean up in the different configurations for > all the projects in CppUnit (was somewhat a mess). That means that > everything should compile fine this time. Great! > Also added a small install guide > for VC++: INSTALL-WIN32.txt (by the way, I added it to EXTRA_DIST in > makefile.am, was that the correct things to do?). Yup. > Could you also apply the > process to convert EOL to DOS format when making the dist (as is done for > *.dsw and *.dsp files)? For INSTALL-WIN32 only? Or for everything? > I went trough the bug reports, and corrected somes (#448363, #448332). > Many reported bugs have already been fixed since release 1.5.5 (I'm closing > them). Has the MIPSPro patch been included ? Don't think so. I'll deal with this. > And what about the report that > it does not compile with gcc 3.0 ? Weird. I have built cppunit using GCC 3.0 on IRIX. That bug report is not spectacularly useful. Is there some way we can contact the submitter to ask for more info? -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 |
|
From: Baptiste L. <bl...@cl...> - 2001-09-17 21:53:47
|
Has this patch been integrated ? I remember posting some comment about
that define symbol...
Here is what it does:
---
Compile 1.5.5 on alpha-dec-osf4.0
To compile on alpha with cxx V6.1-029 you may have to
export DEC_CXX="-D__USE_STD_IOSTREAM -D__STD_MS"
This moves ostream to namespace std and prevents class exception to specify
throw()
Note that I have been using the RougeWave STL implementation. I'm not sure
if this is the default that is
shipped with cxx.
---
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).
|
|
From: Baptiste L. <bl...@cl...> - 2001-09-17 21:43:39
|
> Okay, then. For the unix side, I think everything is basically there.
> I will check that it works on IRIX and maybe freebsd if I get the
> time, but I don't anticipate changing anything other than READMEs,
> NEWS and minor release stuff.
>
> However, I know nothing about the MS windows side of things.
> Baptiste? Can you check things out and let me know whether
> anything needs fixing?
Well, I just did some major clean up in the different configurations for
all the projects in CppUnit (was somewhat a mess). That means that
everything should compile fine this time. Also added a small install guide
for VC++: INSTALL-WIN32.txt (by the way, I added it to EXTRA_DIST in
makefile.am, was that the correct things to do?). Could you also apply the
process to convert EOL to DOS format when making the dist (as is done for
*.dsw and *.dsp files)?
I like it if another VC++ user could grab the last CVS version and get a
rain check on this. For the last release it compiled fine for me, but not
everybody ! Any volunteer ?
I went trough the bug reports, and corrected somes (#448363, #448332).
Many reported bugs have already been fixed since release 1.5.5 (I'm closing
them). Has the MIPSPro patch been included ? And what about the report that
it does not compile with gcc 3.0 ?
Still haven't heard from Patrick about the DSPlugIn (can't get it to
work with VC++). But that is not a blocking issue (we just can not use that
functionnality).
I will try that version of CppUnit tomorrow at work where I have better
test suites.
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).
|
|
From: Baptiste L. <bl...@cl...> - 2001-09-15 18:43:27
|
----- Original Message -----
From: "Steve M. Robbins" <ste...@vi...>
To: "Baptiste Lepilleur" <bl...@cl...>
Cc: "Bastiaan Bakker" <bas...@li...>
Sent: Friday, September 14, 2001 10:35 PM
Subject: Re: [Cppunit-devel] Is this project dead?
[...]
> > What mess are you refering to ?
>
> I was thinking particularly of the documentation when I wrote that.
> The main reason to introduce a "fixture" class is to simplify and
> rationalize the documentation. I only got partway into incorporating
> the Fixture class, and the documentation was either left as-is or
> commented out. In short: it is a mess.
>
> It's been a while since I looked at this stuff, but my impression is
> that it is quicker to just back out of the change than to go forward.
[...]
> > The HelperMacros needs to be update though.
>
> Yes, probably. I only use the CPPUNIT_TEST_SUITE, CPPUNIT_TEST,
> CPPUNIT_TEST_SUITE_END, and CPPUNIT_TEST_SUITE_REGISTRATION. They
> work, but I have no clue about the other macros.
The guilty is the registerTests() method defined in CPPUNIT_TEST_SUITE.
It take a TestFactory as a second parameter, and use that factory to
instantiate the fixture. This factory is declared in the CPPUNIT_TEST_END
macro. All this is done to allow a fixture that subclass another one to call
its parent fixture registerTests() method while passing its factory that
will instantiate the subclass fixture, and not the parent fixture, for each
test case.
This mecanism was introduced somewhere after CppUnit 1.5.5 I think, to
replace the use of method which are ill supported (It need a workaround just
to compile with VC++).
Since the fixture won't be Test anymore, we won't be able to use the
TestFactory as a base class for factory. That why I planned to introduce a
TestFixture class.
> > I was planning to introduce a TestFixtureFactory to replace the existing
> > TestFactory since Test can't be used as a base class for TestFixture
> > anymore.
> >
> > May be those change should be postponed after the release ?
>
> At this point, I think it would be fastest to back out of all the
> fixture stuff and make the release. Reorganizing the architecture
> turned out to be a much bigger job than I had expected.
OK, let's postpone TestFixture stuff after the release. In addition
to the doc, the examples should also be updated (they all use TestCase as a
base class).
> P.S. By offering to maintain CppUnit in my message yesterday, I was
> in no way trying to pre-empt anyone. If Baptiste or anyone else wants
> the job, they can have it. I have far too many other things to do. I
> offer myself as a candidate of last resort ;-) because I do want to
> see CppUnit continue development.
Unfortunately, I don't have the skill to maintain a Unix project. I know
how to build a project, but I barely have a clue about maintaining those
configure/makefile script.
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).
|