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


On 10/19/2014 05:22 PM, Robert Antoni Buj i Gelonch wrote:
The previous message was for the master branch, the next output was
obtained in 4.3 branch:

There are two situations to consider:

1 Genuine LO code links against an external dylib A. A's install name needs to contain a special filepath segment denoting where A is located in the installset, see the comment at the top of solenv/bin/macosx-change-install-names.pl and e.g.

                $(if $(filter 
MACOSX,$(OS)),--prefix=/@.__________________________________________________OOO) \

in external/cairo/ExternalProject_cairo.mk.

2 An external dylib B links against another external dylib A (from the same or another external project). A needs to be set up according to (1). The ExternalProject_*.mk for B needs to explicitly call macosx-change-install-names on B, see e.g.

                $(if $(filter MACOSX,$(OS)),&& $(PERL) \
                        $(SRCDIR)/solenv/bin/macosx-change-install-names.pl shl OOO \
                        
$(gb_Package_SOURCEDIR_icu)/source/lib/libicudata$(gb_Library_DLLEXT).$(icu_VERSION) \
                        
$(gb_Package_SOURCEDIR_icu)/source/lib/libicuuc$(gb_Library_DLLEXT).$(icu_VERSION) \
                        
$(gb_Package_SOURCEDIR_icu)/source/lib/libicui18n$(gb_Library_DLLEXT).$(icu_VERSION)) \

in external/icu/ExternalProject_icu.mk.

Stephan

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.