On 23/09/13 15:22, Stephan Bergmann wrote:
The ideal with the recent move to instdir would of course be to run
CppunitTests against instdir (as the---premature?---move of
cppunittester to instdir manifests).
the only reason why that (and a bunch of test libraries) is in instdir
is the LibreOffice_Test installation set actually packages it. i don't
know if anybody needs that.
Yet another caveat is that those CppunitTests can run against varyingly
"filled" instdirs, and thus behave subtly differently should they ever
start to pick up the various bootstrap variables defined across instdir
(which reference stuff in instdir that might or might not yet be there).
how is that different from running against a partially filled solver?
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.