On Fri, May 18, 2012 at 11:40:13AM +0300, Tor Lillqvist wrote:
This is a good idea, but I think it would be even better to have
autogen.lastrun.build (or whatever you want to call it). Then we would
not need to specify _any_ build-specific options for the host configure.
Opinions?
I don't think that would be easy to implement,
Why not? Changing the inner configure call to
./configure `cat configure.lastrun.build`
seems pretty simple (of course there should be check if the file exists
etc.) Or am I missing something?
and in any case, then
we should rename autogen.lastrun to configure.lastun (possibly then
suffixed with .host and .build) to avoid confusion. After all,
autogen.sh is not run twice in a cross-compiling configuration;
configure is.
Yes, that would make sense. I just used the terminology we have now (and
I added "or whatever you want to call it").
D.
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.