On Tue, 2011-10-04 at 11:49 +0200, Stephan Bergmann wrote:
On 10/03/2011 12:45 PM, Caolán McNamara wrote:
A better solution might be to put a stock "libtool" into our tree, patch
it to smuggle the correct gb_LinkTarget__RPATHS entry into the link
line, and then always copy our patched libtool over preexisting libtools
when we unpack "external" tarballs in our build ?
Sounds good to me.
It might all be a bit moot really. We build on windows with msvc, and
configure doesn't know about msvc's command line options, nor does
libtool, so a good bit more work would be required to e.g. teach
autotools about msvc and regenerate configure tool chain with said
modified autotools, and/or use one of the cccl derivatives to wrap msvc
with a script to translate gcc-alike arguments into msvc equivalents.
C.
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.