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
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice