On Sat, May 09, 2015 at 02:31:16PM +0200, David Tardon wrote:
At the very least, you would need to be consistent about passing
--host and --build to the externals:
Cross-compilation support for the bundled projects was added to these
that needed to be cross-compiled. Doing it for all of them would be a
lot of effort for no immediate gain. Instead, people interested in
cross-compilation are expected to fix things themselves.
All of the libraries used on the target machine need to be cross
compiled.
What is your motivation then?
The customer wants this.
The same goes for the many --without-foo and --disable-bar options.
Many of these don't work.
Examples, please?
--enable-python=no
There are others, too. Sorry, I've been through so many bad
combinations, but I didn't keep notes about this.
(I do have more specifics about configure.ac and the makefiles.)
Like I said, at the end I'll try to give feedback about where the
issues are, but I don't expect being able to really clean this all
up. That would be a ton of work.
x86_64
Why?!
Well, the customer is always right, you know. ;^)
Thanks,
Richard
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.