cppunit-devel Mailing List for CppUnit - C++ port of JUnit (Page 52)
Brought to you by:
blep
Menu
▾
▴
cppunit-devel — CppUnit Developer Mailing List
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-14 19:27:39
|
> > But I'm working with Patrick to integrate his VC++ add-in patch (mostly
> > done). Some warning and compilation issue have also been fixed for VC++.
> > Those will in my next commit.
Well, I finally comitted. Patrick's patch is there, but I can't get VC++
to register the add-in. I'm waiting Patrick feedback on that particular
issue.
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-14 19:23:58
|
Huhh, I messed up while replying to Bob. Here is the forward: ----- Original Message ----- From: "Summerwill, Bob" <BSu...@eu...> To: "Baptiste Lepilleur" <bl...@cl...> Sent: Friday, September 14, 2001 10:58 AM Subject: RE: [Cppunit-devel] Is this project dead? > > Thanks for your reply - did you mean to send it just to me? > > I think that the CVS head revision is worth releasing (with minimal rework). > Lots of work appears to be have been carried out since 1.5.5, and it seems a > shame that only people with CVS access can use that. > > Here are the WikiWikiWeb links ... > > http://c2.com/cgi/wiki?CppUnit > http://c2.com/cgi/wiki?EnhancingCppUnit > > Maybe I was jumping to conclusions in thinking that these discussions drove > the rework of Michael Feathers' original version? Anyway, there's some good > stuff there. > > > Cheers, > Bob > > > -----Original Message----- > From: Baptiste Lepilleur [mailto:bl...@cl...] > Sent: 13 September 2001 22:54 > To: Summerwill, Bob > Subject: Re: [Cppunit-devel] Is this project dead? > > > I came back from holiday a short while ago, and I've been quiet busy since > then. > > But I'm working with Patrick to integrate his VC++ add-in patch (mostly > done). Some warning and compilation issue have also been fixed for VC++. > Those will in my next commit. > > Could you provide a link to the WikiWikiWeb ? > > There was a discussion in July about a release. If we do one know, then the > large change will come in the next version (restructuring the include > directory hierarchy, and using namespace in the TestRunners). But may be we > should just give it a go. > > ----- Original Message ----- > From: "Summerwill, Bob" <BSu...@eu...> > To: <cpp...@li...> > Sent: Thursday, September 13, 2001 3:30 PM > Subject: [Cppunit-devel] Is this project dead? > > > > I was very pleased to see that CppUnit had been updated this summer, > > following the suggested improvements on the WikiWikiWeb. The activity > stats > > show the rapid decline in August and September. Is there going to be a > new > > release in the near future? Are patches or suggestions being examined? > Is > > anyone there? > > > > > > Cheers, > > Bob > > > |
|
From: Summerwill, B. <BSu...@eu...> - 2001-09-14 09:11:45
|
Thanks for your replies. The e-mail wasn't intended as any personal criticism, and I hope it wasn't taken that way ;-) I've been using the CVS head revision for a week or two. There are a few months worth of good work in there, and it seems a shame that there hasn't been a public release in that time. I had to make a few minor modifications to get clean builds on MSVC++ 6.0, but the changes were very minimal (and detailed in a previous mail to this group). Bastiaan> Such are the difficulties of volunteer based projects.... Bastiaan> If you like to help, don't hesitate to say so! I'd like to help but (like yourself, Bastiaan) due to circumstances beyond my control, it turns out that I'm unlikely to be using CppUnit regularly in the future. Sorry ... Cheers, Bob -----Original Message----- From: Steve M. Robbins [mailto:ste...@vi...] Sent: 14 September 2001 00:01 To: cpp...@li... Subject: Re: [Cppunit-devel] Is this project dead? On Thu, Sep 13, 2001 at 11:44:54PM +0200, Bastiaan Bakker wrote: > To answer your question: I plan to build a new release soon (this > weekend or next week). Hi Bastiaan: I have to confess that I screwed with a couple of things in CVS way back in July and haven't put them right yet. Following the discussions on test fixtures, I introduced TestFixture.h and intended to recode TestCase to use it. Unfortunately, I got distracted and haven't finished all that work yet. If you prefer to revert these changes, I won't be offended. In fact, I have been planning to revert the change myself. I'll try to do so this weekend, unless I hear otherwise from you. > Unfortunately that probably will my last release > at the same time: when I took up maintainership of CppUnit half a year > ago, I' was planning to use very soon, but things worked out > differently. Maintaining a package you don't use your self turns out to > be neither efficient nor effective. So I'm looking for someone to take > over my job. A 'help wanted' request will be attached to the next release. > I would like to add that Baptiste and Steven have performed a large > chunk of the work in the recent releases. I do not know how much time > they can or want to devote to CppUnit in the future however. I'm here. I'm still interested in CppUnit development: I've been using CppUnit for my coding since June. One reason that I haven't done any work on cppunit is that I have gotten used to many of its quirks. If no-one else volunteers, I can certainly make releases of CppUnit. I'm still around to work on CVS, in any case. -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 |
|
From: Steve M. R. <ste...@vi...> - 2001-09-13 23:01:08
|
On Thu, Sep 13, 2001 at 11:44:54PM +0200, Bastiaan Bakker wrote: > To answer your question: I plan to build a new release soon (this > weekend or next week). Hi Bastiaan: I have to confess that I screwed with a couple of things in CVS way back in July and haven't put them right yet. Following the discussions on test fixtures, I introduced TestFixture.h and intended to recode TestCase to use it. Unfortunately, I got distracted and haven't finished all that work yet. If you prefer to revert these changes, I won't be offended. In fact, I have been planning to revert the change myself. I'll try to do so this weekend, unless I hear otherwise from you. > Unfortunately that probably will my last release > at the same time: when I took up maintainership of CppUnit half a year > ago, I' was planning to use very soon, but things worked out > differently. Maintaining a package you don't use your self turns out to > be neither efficient nor effective. So I'm looking for someone to take > over my job. A 'help wanted' request will be attached to the next release. > I would like to add that Baptiste and Steven have performed a large > chunk of the work in the recent releases. I do not know how much time > they can or want to devote to CppUnit in the future however. I'm here. I'm still interested in CppUnit development: I've been using CppUnit for my coding since June. One reason that I haven't done any work on cppunit is that I have gotten used to many of its quirks. If no-one else volunteers, I can certainly make releases of CppUnit. I'm still around to work on CVS, in any case. -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: Bastiaan B. <bas...@li...> - 2001-09-13 21:44:45
|
Hi Bob, Open Source projects don't die, they just fade away into obsolence :-) To answer your question: I plan to build a new release soon (this weekend or next week). Unfortunately that probably will my last release at the same time: when I took up maintainership of CppUnit half a year ago, I' was planning to use very soon, but things worked out differently. Maintaining a package you don't use your self turns out to be neither efficient nor effective. So I'm looking for someone to take over my job. A 'help wanted' request will be attached to the next release. I would like to add that Baptiste and Steven have performed a large chunk of the work in the recent releases. I do not know how much time they can or want to devote to CppUnit in the future however. Such are the difficulties of volunteer based projects.... If you like to help, don't hesitate to say so! Regards, Bastiaan Summerwill, Bob wrote: > I was very pleased to see that CppUnit had been updated this summer, > following the suggested improvements on the WikiWikiWeb. The activity > stats show the rapid decline in August and September. Is there going > to be a new release in the near future? Are patches or suggestions > being examined? Is anyone there? > > > > > > Cheers, > > Bob > |
|
From: Summerwill, B. <BSu...@eu...> - 2001-09-13 13:30:57
|
I was very pleased to see that CppUnit had been updated this summer, following the suggested improvements on the WikiWikiWeb. The activity stats show the rapid decline in August and September. Is there going to be a new release in the near future? Are patches or suggestions being examined? Is anyone there? Cheers, Bob |
|
From: <bob...@ya...> - 2001-09-04 23:30:50
|
When I build the CVS HEAD version of CppUnit using MSVC++ 6.0, I get some warnings in TestFactoryRegistry.cpp. These appear to have been introduced in version 1.4 of Portability.h, when the OStringStream class was added, as there is now a <string> #include prior to the VC++ #pragma disable. At the same time, version 1.11 of TestFactoryRegistry.cpp moved <utility> above <CppUnit/Portability.h>, which causes the same problem. For the VC++ build at least, the <utility> #include doesn't seem to be needed in that CPP and can safely be removed. Hope that's helpful. Cheers, Bob ===== e-mail: bo...@su... website: http://www.summerwill.net ____________________________________________________________ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie |
|
From: Patrick H. <pa...@13...> - 2001-08-30 15:01:16
|
I completely understand--I just went through that in April. Good luck with everything. I look forward to the new release. -Patrick cpp...@li... wrote: } Hi Patrick, } } I've been rather busy with finishing up the last things for my Masters } Degree, but I should have more time starting next week. I hope to review } your patch then and do a new CppUnit release as well. } } Thanks, } } Bastiaan } } } } 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. } > } > -Patrick } > } > Patrick L. Hartling | Research Assistant, VRAC } > pa...@13... | 2624 Howe Hall -- (515)294-4916 } > http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ } > } > _______________________________________________ } > Cppunit-devel mailing list } > Cpp...@li... } > http://lists.sourceforge.net/lists/listinfo/cppunit-devel } } } _______________________________________________ } Cppunit-devel mailing list } Cpp...@li... } http://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: Bastiaan B. <bas...@li...> - 2001-08-30 14:55:55
|
Hi Patrick, I've been rather busy with finishing up the last things for my Masters Degree, but I should have more time starting next week. I hope to review your patch then and do a new CppUnit release as well. Thanks, Bastiaan 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. > > -Patrick > > Patrick L. Hartling | Research Assistant, VRAC > pa...@13... | 2624 Howe Hall -- (515)294-4916 > http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ > > _______________________________________________ > Cppunit-devel mailing list > Cpp...@li... > http://lists.sourceforge.net/lists/listinfo/cppunit-devel |
|
From: Patrick H. <pa...@13...> - 2001-08-30 14:43:14
|
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. -Patrick 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: Bastiaan B. <Bas...@li...> - 2001-08-27 09:57:45
|
Hi Volker, I'd say, give the CVS version a try. Most likely the next release will not differ very much from the current CVS HEAD. I plan to build it somewhere next week, when I've finished my Masters'.=20 If you find any problems in the mean time please report them through the mailing list. Regards, Bastiaan > -----Oorspronkelijk bericht----- > Van: vbo...@te... [mailto:vbo...@te...] > Verzonden: Monday, August 27, 2001 10:23 AM > Aan: cpp...@li... > Onderwerp: [Cppunit-devel] Release plan >=20 >=20 > Hi, >=20 > I'ld like to use cppunit for a project starting soon. As I=20 > know a lot of > changes will occur in the next release. So I'ld prefer to use=20 > the newest > version of cppunit to avoid having to change the testcases=20 > due to a later > cppunit update. >=20 > What is your suggestion, should we use the latest CVS=20 > version? Or is there > any activity to finish the work on the next release? >=20 > Regards, > Volker > --=20 > Volker Boerchers <vbo...@te...> > System Engineer > TECON Systems AG, Perlengraben 2, 50676 K=F6ln, http://www.tecon.de > Tel: +49-221-92007-55, Fax: +49-221-92007-77 >=20 >=20 > _______________________________________________ > Cppunit-devel mailing list > Cpp...@li... > http://lists.sourceforge.net/lists/listinfo/cppunit-devel >=20 |
|
From: <vbo...@te...> - 2001-08-27 08:22:53
|
Hi, I'ld like to use cppunit for a project starting soon. As I know a lot of changes will occur in the next release. So I'ld prefer to use the newest version of cppunit to avoid having to change the testcases due to a later cppunit update. What is your suggestion, should we use the latest CVS version? Or is there any activity to finish the work on the next release? Regards, Volker --=20 Volker Boerchers <vbo...@te...> System Engineer TECON Systems AG, Perlengraben 2, 50676 K=F6ln, http://www.tecon.de Tel: +49-221-92007-55, Fax: +49-221-92007-77 |
|
From: David L. L. <da...@WP...> - 2001-08-13 19:46:52
|
I've created a patch to CppUnit 1.5.5 which allows it to be built as a .DLL in MSVC6. This can be found at: http://www.wpi.edu/~davidl/cppunit-1.5.5_msvc-dll.tar.bz2 To apply the patch, you'll need a copy of CygWin. Then use the following commands: * tar xvzf cppunit-1.5.5.tar.gz * bzip2 -dc cppunit-1.5.5_msvc-dll.tar.bz2 | tar xvf - * patch -p0 < cppunit-1.5.5_msvc-dll.diff * cp cppunitdll.dsp cppunit-1.5.5/src/cppunit To use this: * Include cppunitdll.dsp in an MSVC6 workspace. * Link to cppunitdll.lib, which will be located in cppunit-1.5.5/lib * Make sure that CPPUNIT_DLL is defined either via the command line or before any CppUnit header files are included. Using CppUnit as a DLL fixes some bugs when trying to use CppUnit across many different .DLLs. In my case, I wanted to use CppUnit in a project consisting of many different plugins, each of which would have test cases compiled into them. Linking CppUnit statically into each of these files caused numerous problems. Building CppUnit as a .DLL fixed these. -- David Ludwig | "The Linux philosophy is laugh in the face of davidl<at>wpi.edu | danger. Oops. Wrong One. 'Do it yourself.' http://www.wpi.edu/~davidl | That's it." - Linus Torvalds |
|
From: yuwei <s62...@nt...> - 2001-07-26 18:58:42
|
hi everybody, i'm newbie to cppunit. i'm using vc++ as my compiler and i also=20 know there's a mfc tool called "test runner", but i couldn't figuer=20 the usage. is there any document or where can i find futher informaton about this stuff?=20 thanx for ur reply yuwei |
|
From: Baptiste L. <bl...@cl...> - 2001-07-25 18:48:10
|
----- Original Message ----- From: "Laurie Spencer" <la...@sh...> To: <cpp...@li...> Sent: Wednesday, July 25, 2001 1:22 AM Subject: [Cppunit-devel] AFX_EXT_CLASS error > We're just starting with cppunit - any help would be greatly appreciated! > > We are trying to move forward to unit testing with legacy code. I finally > got everything to link happily and created a test case and that compiles and > links fine. > > I copied > static AFX_EXTENSION_MODULE extTestRunner; Huu, What's that ? To use TestRunner, you only need: #include <msvc6/testrunner/TestRunner.h> You must also define the symbol _AFX_DLL (see notes in TestRunner.h in the CVS version). This is usually done by default when you create a new project with VC++. 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: Laurie S. <la...@sh...> - 2001-07-24 23:22:02
|
We're just starting with cppunit - any help would be greatly appreciated!
We are trying to move forward to unit testing with legacy code. I finally
got everything to link happily and created a test case and that compiles and
links fine.
I copied
static AFX_EXTENSION_MODULE extTestRunner;
and then I copied the code out of HostApp
BOOL CHostAppDoc::OnNewDocument()
{
if (!CDocument::OnNewDocument())
return FALSE;
TestRunner runner;
runner.addTest
( CppUnit::TestFactoryRegistry::getRegistry().makeTest() );
runner.run ();
return TRUE;
}
to my OnNewDocument() function to start the test and I am now baffled why my
code does not compile, I can't see any important differences from the
HostApp project - it gives me the error
c:\projects\cppunit\cppunit-1.5.5\include\msvc6\testrunner\testrunner.h(20)
: error C2079: 'TestRunner' uses undefined class 'AFX_EXT_CLASS'
I am using VC++ 6.0 and cppunit 1.5.5 (with the latest TestRunner.h from
cvs).
Thank you for any help!
Laurie
|
|
From: Lynn J. <lw...@sh...> - 2001-07-24 18:46:44
|
We are using some fixes to the stl library, as well as using a couple other static libraries of packages we are using. I'm not sure we have all the source to build stl into a dll, but we'll look into it. Thanks again for your answer, Lynn Baptiste Lepilleur wrote: > > No. > You'll need to add your own configuration or change the existing one. > > Is there a specific reason for using static debug lib ? DLL should link > faster (this is a wild guess, I never actually measured). > > ----- Original Message ----- > From: "Lynn Jones" <lw...@sh...> > To: <cpp...@li...> > Sent: Tuesday, July 24, 2001 1:00 AM > Subject: Re: [Cppunit-devel] link errors with stl > > > Thank you for your reply. We were using these settings, but have > > determined that they are incompatible with the settings required > > by the rest of our project. Is there an available cppunit/testrunner > > project with target of a static library rather than a DLL? Or is that > > possible? > > > > Thanks! > > Lynn > > > > Baptiste Lepilleur wrote: > > > > > > ----- Original Message ----- > > > From: "Baptiste Lepilleur" <bl...@cl...> > > > To: <cpp...@li...> > > > Sent: Saturday, July 21, 2001 11:23 AM > > > Subject: Re: [Cppunit-devel] link errors with stl > > > > > > > Most likely, you are not using the same CRT lib as cppunit. You must > use > > > the > > > > Debug Multithreaded CRT lib (Project Setting/C++/Code Generation). > > > > Don't forget to enable RTTI too (Project Setting/C++/C++ Langage). > > > > > > Read Debug Multithreaded **DLL** > > > > > > Sorry, > > > 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... > http://lists.sourceforge.net/lists/listinfo/cppunit-devel -- Lynn Jones AI Software Engineer, SHAI-Seattle lw...@sh... |
|
From: Baptiste L. <bl...@cl...> - 2001-07-24 18:30:21
|
No. You'll need to add your own configuration or change the existing one. Is there a specific reason for using static debug lib ? DLL should link faster (this is a wild guess, I never actually measured). ----- Original Message ----- From: "Lynn Jones" <lw...@sh...> To: <cpp...@li...> Sent: Tuesday, July 24, 2001 1:00 AM Subject: Re: [Cppunit-devel] link errors with stl > Thank you for your reply. We were using these settings, but have > determined that they are incompatible with the settings required > by the rest of our project. Is there an available cppunit/testrunner > project with target of a static library rather than a DLL? Or is that > possible? > > Thanks! > Lynn > > Baptiste Lepilleur wrote: > > > > ----- Original Message ----- > > From: "Baptiste Lepilleur" <bl...@cl...> > > To: <cpp...@li...> > > Sent: Saturday, July 21, 2001 11:23 AM > > Subject: Re: [Cppunit-devel] link errors with stl > > > > > Most likely, you are not using the same CRT lib as cppunit. You must use > > the > > > Debug Multithreaded CRT lib (Project Setting/C++/Code Generation). > > > Don't forget to enable RTTI too (Project Setting/C++/C++ Langage). > > > > Read Debug Multithreaded **DLL** > > > > Sorry, > > 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: Lynn J. <lw...@sh...> - 2001-07-23 23:00:15
|
Thank you for your reply. We were using these settings, but have determined that they are incompatible with the settings required by the rest of our project. Is there an available cppunit/testrunner project with target of a static library rather than a DLL? Or is that possible? Thanks! Lynn Baptiste Lepilleur wrote: > > ----- Original Message ----- > From: "Baptiste Lepilleur" <bl...@cl...> > To: <cpp...@li...> > Sent: Saturday, July 21, 2001 11:23 AM > Subject: Re: [Cppunit-devel] link errors with stl > > > Most likely, you are not using the same CRT lib as cppunit. You must use > the > > Debug Multithreaded CRT lib (Project Setting/C++/Code Generation). > > Don't forget to enable RTTI too (Project Setting/C++/C++ Langage). > > Read Debug Multithreaded **DLL** > > Sorry, > 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... > http://lists.sourceforge.net/lists/listinfo/cppunit-devel -- Lynn Jones AI Software Engineer, SHAI-Seattle lw...@sh... |
|
From: Baptiste L. <bl...@cl...> - 2001-07-21 09:25:25
|
----- Original Message ----- From: "Baptiste Lepilleur" <bl...@cl...> To: <cpp...@li...> Sent: Saturday, July 21, 2001 11:23 AM Subject: Re: [Cppunit-devel] link errors with stl > Most likely, you are not using the same CRT lib as cppunit. You must use the > Debug Multithreaded CRT lib (Project Setting/C++/Code Generation). > Don't forget to enable RTTI too (Project Setting/C++/C++ Langage). Read Debug Multithreaded **DLL** Sorry, 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-07-21 09:07:40
|
Most likely, you are not using the same CRT lib as cppunit. You must use the Debug Multithreaded DLL CRT lib (Project Setting/C++/Code Generation). Don't forget to enable RTTI too (Project Setting/C++/C++ Langage). ----- Original Message ----- From: "Lynn Jones" <lw...@sh...> To: <cpp...@li...> Sent: Friday, July 20, 2001 10:43 PM Subject: [Cppunit-devel] link errors with stl > Hi, > > I was reading Ferdinando Ametrano's notes about using cppunit > (msg #6221559) and am having a similar linking problem. I am using > MSVC 6.0 on Win2K. I have successfully built the cppunitd and > testrunnerd libraries, but am getting the linking error when I > try to subclass TestCase in my own project (which uses stl classes). > > Any suggestions on fixing this problem? > > Thanks! > Lynn > -- > Lynn Jones > AI Software Engineer, SHAI-Seattle > lwjones at shai-seattle dot com > > _______________________________________________ > Cppunit-devel mailing list > Cpp...@li... > http://lists.sourceforge.net/lists/listinfo/cppunit-devel > |
|
From: Baptiste L. <bl...@cl...> - 2001-07-21 09:06:04
|
Most likely, you are not using the same CRT lib as cppunit. You must use the Debug Multithreaded CRT lib (Project Setting/C++/Code Generation). Don't forget to enable RTTI too (Project Setting/C++/C++ Langage). ----- Original Message ----- From: "Lynn Jones" <lw...@sh...> To: <cpp...@li...> Sent: Friday, July 20, 2001 10:43 PM Subject: [Cppunit-devel] link errors with stl > Hi, > > I was reading Ferdinando Ametrano's notes about using cppunit > (msg #6221559) and am having a similar linking problem. I am using > MSVC 6.0 on Win2K. I have successfully built the cppunitd and > testrunnerd libraries, but am getting the linking error when I > try to subclass TestCase in my own project (which uses stl classes). > > Any suggestions on fixing this problem? > > Thanks! > Lynn > -- > Lynn Jones > AI Software Engineer, SHAI-Seattle > lwjones at shai-seattle dot com > > _______________________________________________ > Cppunit-devel mailing list > Cpp...@li... > http://lists.sourceforge.net/lists/listinfo/cppunit-devel > |
|
From: Lynn J. <lw...@sh...> - 2001-07-20 20:43:14
|
Hi, I was reading Ferdinando Ametrano's notes about using cppunit (msg #6221559) and am having a similar linking problem. I am using MSVC 6.0 on Win2K. I have successfully built the cppunitd and testrunnerd libraries, but am getting the linking error when I try to subclass TestCase in my own project (which uses stl classes). Any suggestions on fixing this problem? Thanks! Lynn -- Lynn Jones AI Software Engineer, SHAI-Seattle lwjones at shai-seattle dot com |
|
From: Ferdinando A. <ml...@am...> - 2001-07-20 14:21:17
|
Hi all thank you everybody for the feedback to my last email. >I would suggest that you use the CVS version of CppUnit, and keep abreast of >this mailing list, as the API, such as it is, is very fluid at the moment. Ok I checked out the CVS version, I will stay tuned. >When you say "make failed", do you mean that it really stopped with an >error message? Or do you mean that it failed to generate the documentation? It stopped with: Making all in doc make[1]: Entering directory `/cygdrive/e/cppunit-1.5.5/doc' /cygdrive/e/Program Files/doxygen-1.2.8.1/bin/doxygen /cygdrive/e/Program: not found make[1]: *** [html/index.html] Error 127 make[1]: Leaving directory `/cygdrive/e/cppunit-1.5.5/doc' make: *** [all-recursive] Error 1 Anyway it just failed the documentation part. Everything else seems fine, except maybe the following warning: /bin/sh ../../libtool --mode=link c++ -O2 -o libcppunit.la -rpath /usr/local/lib -version-info 5:0:0 -release 1.5 TestAssert.lo TestCase.lo TestSuite.lo TestResult.lo TestFailure.lo TestRegistry.lo Exception.lo TextTestResult.lo TestFactoryRegistry.lo TypeInfoHelper.lo libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin shared libraries > > I would humbly suggest to have a different directive for document > > generation, something like: > > if DOXYGEN_FOUND > > docs: > > $(DOXYGEN) Doxyfile.in > > else > > docs: > > echo You need to install doxygen in order to generate > > documentation. > > endif > >Hmm, I don't see where things go wrong: if configure cannot detect doxygen >or it has been disabled with '--without-doxygen' the 'doc' subdir will be >excluded from the build, so no attempt to run doxygen will be made. Only if >you explicitly do 'make docs', you'll get an error. The problem is that configure detects my doxygen under E:\Program Files\doxygen, then when make tries to use doxygen it fails because it cannot find E:\Program: I tried to run configure --without-doxygen but I had similar results. Configure prints out: checking for doxygen... /cygdrive/e/Program Files/doxygen-1.2.8.1/bin/doxygen test: Files/doxygen-1.2.8.1/bin/doxygen: unknown operand checking for dot... /cygdrive/e/Program Files/graphviz/bin/dot test: Files/graphviz/bin/dot: unknown operand then make will fail as above while trying to build documentation. So I cannot avoid the documentation step. > > I would humbly suggest to have a different directive for document > > generation, something like: > > if DOXYGEN_FOUND > > docs: > > $(DOXYGEN) Doxyfile.in > > else > >Something similar to this is done. Err, maybe only in CVS, though... Unfortunately cygwin does not include libtool, so I cannot execute the autogen script. I should use a real Linux box, but my Mandrake box is currently down > > 4) It would be nice to have a Win32 binary visual installer. This can be > > easily supported with NSIS (http://www.nullsoft.com/free/nsis/). NSIS is > > free and it is script driven. I could help creating the cppunit installer > > script, if somebody help me to select which *.h is needed, etc. > What would this bring for the user ? I'd rather have a tar ball or a zip >file which I can explore than a big binary platform specific file. End user >of the library are developer, so I don't think they have too much problem >depacking a file ;-) I would like to have a tarball/zipfile *and* a binary installer. With a binary installer I could have started using cppunit in my project immediately (I just need a lib and few header files), then later I could have take a look at the source code. >Feel free to to contribute an NSIS script for installation! I'll try to came up with a proposal > > 2) I opened TestRunner.dsw and I tried to compile the project TestRunner. > > The first errors were because of the inclusion directive > > #include <cppunit/extensions/TestDecorator.h> > > Adding the cppunit/include path to the project didn't help, I had to add >it > > to my VS settings, as if I had installed cppunit (probably because of the ><>) > > Then I got linking errors. If I've been naive please help me (I can post > > the error messages if needed) > Another user have reported having problem compiling cppunit 1.5.5. The >problem did not occur for him using the CVS version. That problem kind of >bother me since it does seem to occurs only for a few people. I've never >been able to reproduce it either at work or at home). What's your >configuration ? My configuration is Pentium III 700Mhz, NT 4.0 (patch 6), Visual C++ 6.0 The link error is: Generating Code... Linking... msvcprt.lib(MSVCP60.dll) : error LNK2005: "private: bool __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::_Grow(unsigned int,bool)" (?_Grow@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AAE _NI_N@Z) already defined in cppunit.lib(TestSuite.obj) msvcprt.lib(MSVCP60.dll) : error LNK2005: "public: __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::~basic_string<char,struct std::char_traits<char>,class std::allocator<char> >(void)" (??1?$basic_string@ DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@XZ) already defined in cppunit.lib(TestSuite.obj) msvcprt.lib(MSVCP60.dll) : error LNK2005: "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > & __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::assign(class s td::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,unsigned int,unsigned int)" (?assign@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAEAAV12@ABV12@II@Z) already defined in cppunit.lib(TestSuite. obj) msvcprt.lib(MSVCP60.dll) : error LNK2005: "private: void __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::_Copy(unsigned int)" (?_Copy@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AAEXI@Z) already defined in cppunit.lib(TestSuite.obj) msvcprt.lib(MSVCP60.dll) : error LNK2005: "private: void __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::_Tidy(bool)" (?_Tidy@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AAEX_N@Z) alread y defined in cppunit.lib(TestSuite.obj) msvcprt.lib(MSVCP60.dll) : warning LNK4006: "private: bool __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::_Grow(unsigned int,bool)" (?_Grow@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@A AE_NI_N@Z) already defined in cppunit.lib(TestSuite.obj); second definition ignored msvcprt.lib(MSVCP60.dll) : warning LNK4006: "public: __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::~basic_string<char,struct std::char_traits<char>,class std::allocator<char> >(void)" (??1?$basic_strin g@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@XZ) already defined in cppunit.lib(TestSuite.obj); second definition ignored msvcprt.lib(MSVCP60.dll) : warning LNK4006: "public: class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > & __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::assign(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,unsigned int,unsigned int)" (?assign@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAEAAV12@ABV12@II@Z) already defined in cppunit.lib(TestSuit e.obj); second definition ignored msvcprt.lib(MSVCP60.dll) : warning LNK4006: "private: void __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::_Copy(unsigned int)" (?_Copy@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AAEXI@ Z) already defined in cppunit.lib(TestSuite.obj); second definition ignored msvcprt.lib(MSVCP60.dll) : warning LNK4006: "private: void __thiscall std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >::_Tidy(bool)" (?_Tidy@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AAEX_N@Z) alre ady defined in cppunit.lib(TestSuite.obj); second definition ignored Creating library Release/TestRunner.lib and object Release/TestRunner.exp LINK : warning LNK4098: defaultlib "LIBCMT" conflicts with use of other libs; use /NODEFAULTLIB:library TestRunnerDlg.obj : error LNK2001: unresolved external symbol __imp__timeGetTime@0 Release/TestRunner.dll : fatal error LNK1120: 1 unresolved externals Error executing link.exe. Using the version under CVS I had no problem with the "Win32 - Debug" and "Win32 - Debug Crossplatform Settings" configurations. "Win32 - Release" fails because it misses ..\..\..\include and ..\..\..\include\msvc6 as additonal include directories. I added them and it worked fine: you may consider fixing this in the CVS version of TestRunner.dsp diff -r1.7 TestRunner.dsp 47c47 < # ADD CPP /nologo /MD /W3 /GX /O2 /D "NDEBUG" /D "_WINDOWS" /D "_WINDLL" /D "_AFXDLL" /D "_AFXEXT" /D "WIN32" /Yu"stdafx.h" /FD /c --- > # ADD CPP /nologo /MD /W3 /GX /O2 /I "..\..\..\include" /I "..\..\..\include\msvc6" /D "NDEBUG" /D "_WINDOWS" /D "_WINDLL" /D "_AFXDLL" /D "_AFXEXT" /D "WIN32" /Yu"stdafx.h" /FD /c later ciao -- Nando |
|
From: Baptiste L. <bl...@cl...> - 2001-07-17 18:44:41
|
----- Original Message -----
From: "Ferdinando Ametrano" <fer...@am...>
To: <cpp...@li...>
Sent: Monday, July 16, 2001 4:01 PM
Subject: [Cppunit-devel] A few notes about my first experience with cppunit.
> 2) I opened TestRunner.dsw and I tried to compile the project TestRunner.
> The first errors were because of the inclusion directive
> #include <cppunit/extensions/TestDecorator.h>
> Adding the cppunit/include path to the project didn't help, I had to add
it
> to my VS settings, as if I had installed cppunit (probably because of the
<>)
> Then I got linking errors. If I've been naive please help me (I can post
> the error messages if needed)
Another user have reported having problem compiling cppunit 1.5.5. The
problem did not occur for him using the CVS version. That problem kind of
bother me since it does seem to occurs only for a few people. I've never
been able to reproduce it either at work or at home). What's your
configuration ?
>
> 4) It would be nice to have a Win32 binary visual installer. This can be
> easily supported with NSIS (http://www.nullsoft.com/free/nsis/). NSIS is
> free and it is script driven. I could help creating the cppunit installer
> script, if somebody help me to select which *.h is needed, etc.
What would this bring for the user ? I'd rather have a tar ball or a zip
file which I can explore than a big binary platform specific file. End user
of the library are developer, so I don't think they have too much problem
depacking a file ;-) What is really missing is some guide (what project is
what, how to build it...) :-(...
The tar ball "maker" already use a mecanism to select which file are
needed, so I'd rather not want to duplicate the work each time a file is
added (we forgot often enough as it is), unless there is some really meaning
value for it.
Baptiste.
---
Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html
Author of The Text Reformatter, a tool for fanfiction readers and writers.
Language: English, French (Well, I'm French).
|
180 messages has been excluded from this view by a project administrator.
