On 09/05/12 10:02, d.ostrovsky@idaia.de wrote:
Hi,
+1 for this.
This simplify enormously the whole build.
+1 from me as well: i cannot really believe how many man-hours were
spent so far on trying to get this Cygwin path conversion nonsense to
actually work, and apparently it still doesn't, so getting rid of it
sounds like the way to go.
The only question is, can we require, that all Windows build machines
have make 3.82 installed?
that is a good question :)
certainly the tinderboxes must be updated before this goes in.
Ciao
David
Zitat von Noel Grandin <noel@peralex.com>:
Hi
Any chance we can get this in so I can get my tinderbox running on a
RAM-Drive?
I can confirm it works on my tinderbox at least.
Regards, Noel Grandin.
On 2012-05-06 20:57, Matú? Kukan wrote:
Hello,
These patches allow us to get rid of path conversions in makefiles by
using cygpath -m format.
But this only works with make 3.82, so configure is also changed.
(Only for cygwin)
There are only few exceptions where we need cygpath -u format.
I am not sure if we want this now or later. (after libreoffice-3-6
branch is created ?)
Posting here, so you know about this and can push if that's good.
It should work without problems ;-)
HTH,
Matú?
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Disclaimer: http://www.peralex.com/disclaimer.html
Context
- Re: [HOW-TO] Building LibreOffice on Windows using RAM-Drive (continued)
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.