On 08/24/2015 01:04 PM, Damjan Jovanovic wrote: > Hi > > Since commit 1536730 on 2013-10-29 by alg (Armin Le Grand), AOO hasn't > been able to compile with cppunit present and enabled > (--with-system-cppunit), as at least the basegfx and basebmp modules > both have compile errors and unit test failures. > > I fixed the basegfx compile errors (brackets in wrong places and > extraneous commas in function arguments) in commits 1697461 and > 1697470, but then 6 basegfx units tests still fail, and if I comment > them out, the build fails later with compile errors in basebmp, which > are more complicated as new 3rd and 4th arguments to the > basegfx::tools::importFromSvgD() function are necessary and I am not > sure what they should be. > > Please help. > > Also why hasn't anybody caught this earlier? Do we not usually compile > AOO with cppunit enabled?
I think the answer to this is "no". See a post from a few years ago-- http://markmail.org/message/kmkv7cr5todacdq6 It seems we need some code cleanup to remove the remaining cppunit references. > > Thank you > Damjan If you don't specify anything about cppunit in your config options, you will get a warning that cpppunit will not be used, and thus, no errors. See, for example, config output from linux-32 buildbot -- https://ci.apache.org/builders/openoffice-linux32-nightly/builds/63/steps/configure/logs/stdio -- -------------------------------------------- MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
