Hi Francois,
On Tue, 31 May 2011 23:33:06 +0200
Francois Tigeot <ftigeot@wolfpond.org> wrote:
What you said about the gbuild migration makes sense, but I have the
impression you were thinking about removing completely the suffix.
[...]
The final library name would be the same, it would not be problematic
to remove DLLPOSTFIX a little bit at a time.
what I meant was when you change at:
http://opengrok.libreoffice.org/xref/bootstrap/solenv/gbuild/platform/linux-INTEL.mk#32
gb_Library_DLLPOSTFIX := li
to
gb_Library_DLLPOSTFIX := lo
gbuild will with this one change rename all gbuild libraries from
libfooli.so to libfoolo.so on Linux Intel. And it will assume all
libraries build by the old build system to also be named libbarlo.so
instead of libbarli.so. So if library bar is build by the old build
system and library foo by the new one but links against bar, they would
need to be renamed at the same time.
Given the stuff in tail_build links against pretty much everything,
doing that you would not make you change a little bit at a time, but
in one big move -- at least for a given platform. I also consider that a
not a Bad Thing(tm) given the stuff I said about this causing lots of
rebuilds.
But you will find that out yourself when you start working on this, I
guess. ;)
Best,
Bjoern
--
https://launchpad.net/~bjoern-michaelsen
Context
- Re: [Libreoffice] Platform-specific DLL suffix usefulness (continued)
(message not available)
Re: [Libreoffice] Platform-specific DLL suffix usefulness · Caolán McNamara
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.