On 10/06/14 11:04, Bjoern Michaelsen wrote:
In the long run we might add our local patches to the native make again, if its
worth it (maybe?), but that can be done incrementally. Also incrementally, we
maybe they would provide some additional speedup, although i never liked
the built-in cp patch much :)
well the most important thing for now is that other people can
successfully build with native Win32 make, so we can switch.
might reduce our dependency on cygwin in general (you are still using it as a
POSIX environment, are you?) and slowly move to use/be able to use something
smaller and selfcontained[1] like GnuWin32 or even busybox. Apart from possibly
simplifying build env setup, its always good to have the build system not to
depend too hard on one implementation (cygwin).
perhaps using a native Win32 shell would provide some additional
speed-up over Cygwin's bash... as long as it doesn't require another
significant tweak to the quoting in the commands...
Context
Re: Quantifying the time overhead of Cygwin make · Norbert Thiebaud
Re: Quantifying the time overhead of Cygwin make · Michael Stahl
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.