Thread: RE: [Cppunit-devel] Coming release (was: Is this project dead?)
Brought to you by:
blep
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: 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: 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: 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). |