Windows Build setupTools
mike.ennen at gmail.com
Thu Dec 21 05:40:45 UTC 2017
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
is in fact not working correctly.
Invoking buildSrc/genVSproperties.bat directly prints the correct
However adding some debugging to setupTools it is clear that something is
with it. This is the result:
WINDOWS_VS_PATH=;<SNIP ENTIRE SYSTEM PATH>
This is the reason people are needing to hard-code values for the properties
below the call to setupTools.
I am trying to debug what is actually wrong with setupTools but so far not
progress. I tried this on my local Windows 10 machine and Appveyor VMs and
is the same. I also read at least two mails in this list about needing to
properties, I am assuming it is for the same reason.
I will try and figure out the reason but wanted to at least make this issue
More information about the openjfx-dev