On Jul 21, 2013 6:58 PM, "Thorsten Behrens" <thb@documentfoundation.org>
wrote:
Vishv Brahmbhatt wrote:
Actually I did make right entry in the
makefile('test/Package_unittest.mk')
and also added a test-profile at appropriate
location('test/user-template/user/config/soffice.cfg/simpress/layoutlist.xml').But
this commit<
http://cgit.freedesktop.org/libreoffice/core/commit/?h=feature/gsoc-impresslayout&id=a837a7c573c5f35fbcf7b9375725282496b0f4c9
had
only partially solved the problem(for the unit-test). Because as per my
discussion with Thorsten,it seems that there is some problem with how
"brandbasedir"(i.e vnd.sun.star.expand:$BRAND_BASE_DIR) is expanded for
the
"*unit-test*".
Seems this whole test/user-template/user/config/soffice.cfg thing has
bitrotted - I presume it can go entirely, can you try & do a fresh
build for double-checking?
I'm not aware of that. Normally we need this config for all tests that need
a user profile and run during the build. It might be unnecessary nowadays
but then I'm unaware oft these changes.
The corresponding entry in the makefiles is the use_configuration part
which should be defined in the CppunitTest.Mk
Instead, the impress xml config would need to go to
solver/<platform>/unittest/install/share/... , just like in the
regular install.
Normally the test profile is copied during the build to this directory. At
least that is what I implemented back then but I have no computer here to
check that it is still true.
Regards,
Markus
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.