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


On 4 May 2013 17:41, Riccardo Magliocchetti
<riccardo.magliocchetti@gmail.com> wrote:
i'm trying to do some work finishing --disable-extensions, see attached
patch, unfortunately it does not work.

Hmm, is it a good idea. At least I find the name a bit confusing - if
you are trying by this to not build extensions/ module where no
extension (in the sense of .oxt file) is built - only some libraries
(and no idea what else)
I doubt it makes sense - to not build extensions (the change in
RepositoryModule_host.mk - was it intentional ? ) - but possibly I am
wrong.

At compile time i get these, i assume because extensions module is not
providing anything at all:

cat: workdir/unxlngx6.pro/InstallModuleTarget/scp2/extensions.filelist: File
or directory does not exist
cat: workdir/unxlngx6.pro/InstallModuleTarget/scp2/extensions.filelist: File
or directory does not exist

That's from scp2/InstallScript_setup_osl.mk I think.

: ERROR: Removing file libbiblo.so from file list.

But i have these files both in workdir and solver, e.g:

./workdir/unxlngx6/Headers/Library/libbiblo.so
./workdir/unxlngx6/LinkTarget/Library/libbiblo.so
./workdir/unxlngx6/ExternalHeaders/Library/libbiblo.so
./solver/unxlngx6/lib/libbiblo.so

Any hint?

It should be ./solver/unxlngx6**.pro**/lib/libbiblo.so I guess from
your previous error ?
you need to adapt scp2 if you really don't want this stuff.

Best,
Matus

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.