For Programmers: Free Programming Magazines  


Home > Archive > Extreme Programming > July 2006 > Not able to build cppUnit on cygwin









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Not able to build cppUnit on cygwin
forumer

2006-07-23, 6:57 pm

I'll like to start using cppunit-1.10.2 on cygwin. I use g++ 3.4.4, but
I am having problems building it. I ran ./configure and everything
seemed to go OK. Then when I run "make", I get the following build
errros. These .plo files are actually missing. I'd appreciate help very
much.... Thanks

----

$ make
Making all in src
make[1]: Entering directory `/cygdrive/c/cppunit-1.10.2/src'
Making all in cppunit
make[2]: Entering directory `/cygdrive/c/cppunit-1.10.2/src/cppunit'
Makefile:361: .deps/Asserter.Plo: No such file or directory
Makefile:362: .deps/BeOsDynamicLibraryManager.Plo: No such file or
directory
Makefile:363: .deps/BriefTestProgressListener.Plo: No such file or
directory
Makefile:364: .deps/CompilerOutputter.Plo: No such file or directory
Makefile:365: .deps/DefaultProtector.Plo: No such file or directory
Makefile:366: .deps/DynamicLibraryManager.Plo: No such file or
directory
Makefile:367: .deps/DynamicLibraryManagerException.Plo: No such file or
directory
Makefile:368: .deps/Exception.Plo: No such file or directory
Makefile:369: .deps/Message.Plo: No such file or directory
Makefile:370: .deps/PlugInManager.Plo: No such file or directory
Makefile:371: .deps/PlugInParameters.Plo: No such file or directory
Makefile:372: .deps/Protector.Plo: No such file or directory
Makefile:373: .deps/ProtectorChain.Plo: No such file or directory
Makefile:374: .deps/RepeatedTest.Plo: No such file or directory
Makefile:375: .deps/ShlDynamicLibraryManager.Plo: No such file or
directory
Makefile:376: .deps/SourceLine.Plo: No such file or directory
Makefile:377: .deps/StringTools.Plo: No such file or directory
Makefile:378: .deps/SynchronizedObject.Plo: No such file or directory
Makefile:379: .deps/Test.Plo: No such file or directory
Makefile:380: .deps/TestAssert.Plo: No such file or directory
Makefile:381: .deps/TestCase.Plo: No such file or directory
Makefile:382: .deps/TestCaseDecorator.Plo: No such file or directory
Makefile:383: .deps/TestComposite.Plo: No such file or directory
Makefile:384: .deps/TestDecorator.Plo: No such file or directory
Makefile:385: .deps/TestFactoryRegistry.Plo: No such file or directory
Makefile:386: .deps/TestFailure.Plo: No such file or directory
Makefile:387: .deps/TestLeaf.Plo: No such file or directory
Makefile:388: .deps/TestNamer.Plo: No such file or directory
Makefile:389: .deps/TestPath.Plo: No such file or directory
Makefile:390: .deps/TestPlugInDefaultImpl.Plo: No such file or
directory
Makefile:391: .deps/TestResult.Plo: No such file or directory
Makefile:392: .deps/TestResultCollector.Plo: No such file or directory
Makefile:393: .deps/TestRunner.Plo: No such file or directory
Makefile:394: .deps/TestSetUp.Plo: No such file or directory
Makefile:395: .deps/TestSuccessListener.Plo: No such file or directory
Makefile:396: .deps/TestSuite.Plo: No such file or directory
Makefile:397: .deps/TestSuiteBuilderContext.Plo: No such file or
directory
Makefile:398: .deps/TextOutputter.Plo: No such file or directory
Makefile:399: .deps/TextTestProgressListener.Plo: No such file or
directory
Makefile:400: .deps/TextTestResult.Plo: No such file or directory
Makefile:401: .deps/TextTestRunner.Plo: No such file or directory
Makefile:402: .deps/TypeInfoHelper.Plo: No such file or directory
Makefile:403: .deps/UnixDynamicLibraryManager.Plo: No such file or
directory
Makefile:404: .deps/Win32DynamicLibraryManager.Plo: No such file or
directory
Makefile:405: .deps/XmlDocument.Plo: No such file or directory
Makefile:406: .deps/XmlElement.Plo: No such file or directory
Makefile:407: .deps/XmlOutputter.Plo: No such file or directory
Makefile:408: .deps/XmlOutputterHook.Plo: No such file or directory
make[2]: *** No rule to make target `.deps/XmlOutputterHook.Plo'.
Stop.
make[2]: Leaving directory `/cygdrive/c/cppunit-1.10.2/src/cppunit'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/cygdrive/c/cppunit-1.10.2/src'
make: *** [all-recursive] Error 1


----

Phlip

2006-07-23, 6:57 pm

forumer wrote:

> I'll like to start using cppunit-1.10.2 on cygwin. I use g++ 3.4.4, but
> I am having problems building it. I ran ./configure and everything
> seemed to go OK. Then when I run "make", I get the following build
> errros. These .plo files are actually missing. I'd appreciate help very
> much.... Thanks


CppUnit is rather top-heavy. Try this:

http://unittest-cpp.sourceforge.net/

--
Phlip
[url]http://c2.com/cgi/wiki?ZLand[/url] <-- NOT a blog!!!


forumer

2006-07-23, 6:57 pm


Phlip wrote:
> forumer wrote:
>
>
> CppUnit is rather top-heavy. Try this:
>
> http://unittest-cpp.sourceforge.net/
>
> --
> Phlip
> [url]http://c2.com/cgi/wiki?ZLand[/url] <-- NOT a blog!!!


I tried to install unittest-cpp on Windows XP and run make on it in
cygwin using g++ 3.4.4. Right away I get this error. Any idea what this
could be? I'd just like to have a working unit-test framework....
Thanks

-----
src/AssertException.cpp
src/Test.cpp
src/Test.cpp: In member function `void
UnitTest::Test::Run(UnitTest::TestResult
s&) const':
src/Test.cpp:37: error: ISO C++ forbids braced-groups within
expressions
make: *** [src/Test.o] Error 1

---

Phlip

2006-07-23, 6:57 pm

forumer wrote:

> src/Test.cpp:37: error: ISO C++ forbids braced-groups within
> expressions


The core of the problem is that CygWin has poor support for sigsetjmp().
That function is probably as architecture-specific as fork()!

You should try a different compiler, or a different test rig, such as
CppUnitLite. I will report here when I figure out a workaround.

I have a post to the UnitTest++ mailing list about this. I know the authors
are very responsive to code quality, and they want to support CygWin, so
they will figure out a better fix!

--
Phlip
[url]http://c2.com/cgi/wiki?ZLand[/url] <-- NOT a blog!!!


forumer

2006-07-23, 6:57 pm


Phlip wrote:
> forumer wrote:
>
>
> The core of the problem is that CygWin has poor support for sigsetjmp().
> That function is probably as architecture-specific as fork()!
>
> You should try a different compiler, or a different test rig, such as
> CppUnitLite. I will report here when I figure out a workaround.
>
> I have a post to the UnitTest++ mailing list about this. I know the authors
> are very responsive to code quality, and they want to support CygWin, so
> they will figure out a better fix!
>
> --
> Phlip
> [url]http://c2.com/cgi/wiki?ZLand[/url] <-- NOT a blog!!!


Thank you for your responsiveness. I also posted the same message as
above to the unitTest++ mailing list. I look forward to your follow up
message. I am a C++ newbie and will stay with g++ for now. However,
I'll give CppUnitLite a try as well. I appreciate your suggestions.

Thanks
Satish

Phlip

2006-07-24, 3:57 am

BTW please trim your quotes, for professional-looking posts.

forumer wrote:

> Thank you for your responsiveness. I also posted the same message as
> above to the unitTest++ mailing list. I look forward to your follow up
> message. I am a C++ newbie and will stay with g++ for now. However,
> I'll give CppUnitLite a try as well. I appreciate your suggestions.


I have not directly compared CUL to UnitTest, but the latter is newer and
leaner.

Use this magic spell to get a version with -pedantic turned off:

svn co https://svn.sourceforge.net/svnroot/unittest-cpp unittest-cpp

Don'tcha just love pedantry? ;-)

--
Phlip
[url]http://c2.com/cgi/wiki?ZLand[/url] <-- NOT a blog!!!


Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com