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


On Tue, May 24, 2011 at 1:58 PM, Tor Lillqvist <tlillqvist@novell.com> wrote:
I'm afraid, we'll have to settle to some non-empty string then.

Nah, that is fairly pointless. Either we remove it completely or not at all. Isn't the whole 
purpose of removing it to make the makefilery simpler?

Would also help with cross-compiling on Mac.
When the names would be the same for intel and PPC, you could build an
universal binary using lipo, i.e. first build them seperately and then
just combine the files. (well, in theory at least)

If we keep all the $(DLLPOSTFIX) instances there, but just happen to use the same value for it on 
all platforms (or am empty value), we gain nothing.

But setting DLLPOSTFIX to a random string and building will at least
allow to identify other places in the code where the current ones are
expected..

I tried a
build with known-working sources (a snapshot of master) and it failed
somwhere in javaunohelper with a wrong argument to cp.

Well, that will just have to be fixed then;)

Yes, stuff like this needs to be done before just removing DLLPOSTFIX
from all makefiles :-)

ciao
Christian

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.