Sent from my iPad, please excuse any misspellings
On 04 Jan 2016, at 04:58, Chris Sherlock <chris.sherlock79@gmail.com> wrote:
I’ve done a quick check of the cygwin documentation, and they say the following:
"A few Windows tools, such as find.exe, link.exe andsort.exe, may conflict
with the Cygwin versions make sure that you use the full path (/usr/bin/find)
or that your Cygwin bin directory comes first in your PATH." [1]
1. https://cygwin.com/cygwin-ug-net/using-effectively.html
I’m afraid I’m not at all experienced with the whole gbuild process, and I honestly
dare not touch this because of that complete lack of knowledge - but can someone
check that we are actually doing this on Windows builds?
I can confirm that you can have different problems if cygwin/bin is added to PATH after some of the
windows directories.
I had the problem on one vm, and it went away when I installed a new windows package, simply
because the PATH statement changed.
Changing the PATH is not really part of the build system, it is something you normally do in the
control panel or in the .bashrc (more effectively because it only affects cygwin).
rgds
jan i.
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.