Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


On Mon, May 11, 2015 at 05:57:38PM +0200, Michael Stahl wrote:
On 08.05.2015 16:53, Miklos Vajna wrote:
In any case:

if test "$cross_compiling" != "yes"; then
    libo_CHECK_SYSTEM_MODULE([cppunit],[CPPUNIT],[cppunit >= 1.12.0])
fi

in configure.ac where cppunit is disabled in case of cross-compiling.

If I remove this test, then it works.

the problem is that sal/Executable_cppunittester.mk had a different
conditional, it was wrongly checking for DESKTOP so it's not built on
Android/iOS but is built for any other cross-compilation target,

fixed on master with 26ebcb023ef3d38956085cbb39416e6f148ab351

This does not work for me (cherry picked onto 4403).

--
/mnt/storage/git/libreoffice/unotest/source/cpp/unoexceptionprotector/unoexceptionprotector.cxx:28:29:
 fatal error: cppunit/Message.h: No such file or directory
 #include "cppunit/Message.h"
                             ^
compilation terminated.
/mnt/storage/git/libreoffice/solenv/gbuild/LinkTarget.mk:189: recipe for target 
'/mnt/storage/git/libreoffice/workdir/CxxObject/unotest/source/cpp/unoexceptionprotector/unoexceptionprotector.o'
 failed
make[1]: *** 
[/mnt/storage/git/libreoffice/workdir/CxxObject/unotest/source/cpp/unoexceptionprotector/unoexceptionprotector.o]
 Error 1
make[1]: *** Waiting for unfinished jobs....
Makefile:237: recipe for target 'build' failed
make: *** [build] Error 2


Sorry,
Richard

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.