One of the reasons I would like to eliminate Cygwin is that I believe it causes
more problems than it is worth. For example, lat time I check, there was a
bunch of code in the build scripts to hack paths because Cygwin apparently
wants non-Windows paths on Windows. It’s the “let’s pretend we
I did not try Tom's build instructions however I can contribute that
having Cygwin on Windows 7 and following the build instructions as
posted on the JavaFX build instructions page is not suffcient to result
in a successful build.
The exact error messages I was receiving I posted earlier .
Ah I see now - the properties were not being re-generated simply because
the file windows_tools.properties already existed and "gradle clean" was not
working because I'm not on Cygwin.
Sorry for the noise.
On Thu, Dec 21, 2017 at 1:08 AM, Michael Ennen wrote:
> Thanks for
Thanks for the tip, Tom. I understand that Cygwin is a dependency of
building on Windows but didn't
know that the properties are only configured on a cygwin shell.
I have a pseudo-goal of removing the Cygwin dependency from building
OpenJFX on Windows and
I wonder why Cygwin is necessary for
Hi Michael,
I did not had to setup any special variables and documented my steps at
https://github.com/BestSolution-at/openjfx-build.
I had trouble myself initially but the reason was that I ran the "gradle
sdk" command from within a MSDOS-Shell but you really need to run it
within cygwin.
Some people were reporting that Windows builds are difficult to setup.
I think this is due to the fact that the call to setupTools in
buildSrc/win.gradle
is in fact not working correctly.
Invoking buildSrc/genVSproperties.bat directly prints the correct
properties.
However adding some debugging