Discussion:
Problems building openjfx
f***@swingempire.de
2018-10-31 13:57:03 UTC
Permalink
first try, following the instructions (for win10) at:

that is having downloaded, installed the required tools, added env
vars as desribed.

Then in cygwin, navigate to the git working dir, typing

gradle tasks

fails with:

FAILURE: Build failed with an exception.

* Where:
Script
'C:\Daten\data-for-work\eclipse\gitrep-openjdk\openjdk-jfx\buildSrc\win.gradle' line:
92

* What went wrong:
A problem occurred evaluating script.
FAIL: WINSDK_DIR not defined
to me, it looks the env var WINSDK_DIR is not set - what should go in there?

Thanks, Jeanette

BTW: did I ever mention that I hate command line tools - and they feel
it, fighting back with all they got ;)
f***@swingempire.de
2018-10-31 14:02:45 UTC
Permalink
forgot the link to the instruction page, just in case there's another:

https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-EnvironmentVariables
Post by f***@swingempire.de
that is having downloaded, installed the required tools, added env
vars as desribed.
Then in cygwin, navigate to the git working dir, typing
gradle tasks
FAILURE: Build failed with an exception.
Script
92
A problem occurred evaluating script.
FAIL: WINSDK_DIR not defined
to me, it looks the env var WINSDK_DIR is not set - what should go in there?
Thanks, Jeanette
BTW: did I ever mention that I hate command line tools - and they
feel it, fighting back with all they got ;)
Kevin Rushforth
2018-10-31 14:08:56 UTC
Permalink
One thing that might help diagnose this is to look at is the output of
'build/windows_tools.properties'.

Those env variables should be set automatically by the build if you have
VS 2017 installed in the default location. If you have changed anything
in your system (installed new packages or set different env vars) then
manually "rm -rf build" and try running "gradle" again and see if that
helps.

-- Kevin
Post by f***@swingempire.de
https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-EnvironmentVariables
Post by f***@swingempire.de
that is having downloaded, installed the required tools, added env
vars as desribed.
Then in cygwin, navigate to the git working dir, typing
gradle tasks
FAILURE: Build failed with an exception.
Script
'C:\Daten\data-for-work\eclipse\gitrep-openjdk\openjdk-jfx\buildSrc\win.gradle'
line: 92
A problem occurred evaluating script.
FAIL: WINSDK_DIR not defined
to me, it looks the env var WINSDK_DIR is not set - what should go in there?
Thanks, Jeanette
BTW: did I ever mention that I hate command line tools - and they
feel it, fighting back with all they got ;)
f***@swingempire.de
2018-10-31 14:22:29 UTC
Permalink
thanks for the quick answer :)

hmm, those are nearly all empty:

WINDOWS_VS_DEVENVDIR=
WINDOWS_VS_DEVENVCMD=/VCExpress.exe
WINDOWS_VS_VCINSTALLDIR=
WINDOWS_VS_VSINSTALLDIR=
WINDOWS_VS_MSVCDIR=
WINDOWS_VS_INCLUDE=
WINDOWS_VS_LIB=
WINDOWS_VS_LIBPATH=
WINDOWS_VS_PATH=;C:/java/jdk/open-11/bin;C:/ProgramData/Oracle/Java/javapath;C:/WINDOWS/system32;C:/WINDOWS;C:/WINDOWS/System32/Wbem;C:/WINDOWS/System32/WindowsPowerShell/v1.0/;C:/Program Files/Intel/WiFi/bin/;C:/Program Files/Common Files/Intel/WirelessCommon/;C:/DevTools/openjfx-build/tortoise-hg/;C:/Program
Files/dotnet/;C:/WINDOWS/System32/OpenSSH/;C:/DevTools/gradle/bin;C:/DevTools/ant/bin;C:/Users/kleopatra/AppData/Local/Microsoft/WindowsApps;C:/Users/kleopatra/AppData/Local/GitHubDesktop/bin
WINDOWS_VS_VER=100
WINDOWS_SDK_DIR=
WINDOWS_SDK_VERSION=

actually can't even start my visual vc (community edition) - keeps
telling me that the eval time has expired, isn't it supposed to be free?
Post by Kevin Rushforth
One thing that might help diagnose this is to look at is the output
of 'build/windows_tools.properties'.
Those env variables should be set automatically by the build if you
have VS 2017 installed in the default location. If you have changed
anything in your system (installed new packages or set different env
vars) then manually "rm -rf build" and try running "gradle" again
and see if that helps.
-- Kevin
https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-EnvironmentVariables Zitat von
Post by f***@swingempire.de
that is having downloaded, installed the required tools, added env
vars as desribed.
Then in cygwin, navigate to the git working dir, typing
gradle tasks
FAILURE: Build failed with an exception.
Script
92
A problem occurred evaluating script.
FAIL: WINSDK_DIR not defined
to me, it looks the env var WINSDK_DIR is not set - what should go in there?
Thanks, Jeanette
BTW: did I ever mention that I hate command line tools - and they
feel it, fighting back with all they got ;)
f***@swingempire.de
2018-10-31 14:30:06 UTC
Permalink
okay after deleting the properties and running again, it at least
lists the tasks without error - thanks :)

now will try a real build - expecting all hell breaking loose <g>
Post by f***@swingempire.de
thanks for the quick answer :)
WINDOWS_VS_DEVENVDIR=
WINDOWS_VS_DEVENVCMD=/VCExpress.exe
WINDOWS_VS_VCINSTALLDIR=
WINDOWS_VS_VSINSTALLDIR=
WINDOWS_VS_MSVCDIR=
WINDOWS_VS_INCLUDE=
WINDOWS_VS_LIB=
WINDOWS_VS_LIBPATH=
WINDOWS_VS_PATH=;C:/java/jdk/open-11/bin;C:/ProgramData/Oracle/Java/javapath;C:/WINDOWS/system32;C:/WINDOWS;C:/WINDOWS/System32/Wbem;C:/WINDOWS/System32/WindowsPowerShell/v1.0/;C:/Program Files/Intel/WiFi/bin/;C:/Program Files/Common Files/Intel/WirelessCommon/;C:/DevTools/openjfx-build/tortoise-hg/;C:/Program
Files/dotnet/;C:/WINDOWS/System32/OpenSSH/;C:/DevTools/gradle/bin;C:/DevTools/ant/bin;C:/Users/kleopatra/AppData/Local/Microsoft/WindowsApps;C:/Users/kleopatra/AppData/Local/GitHubDesktop/bin
WINDOWS_VS_VER=100
WINDOWS_SDK_DIR=
WINDOWS_SDK_VERSION=
actually can't even start my visual vc (community edition) - keeps
telling me that the eval time has expired, isn't it supposed to be free?
Post by Kevin Rushforth
One thing that might help diagnose this is to look at is the output
of 'build/windows_tools.properties'.
Those env variables should be set automatically by the build if you
have VS 2017 installed in the default location. If you have changed
anything in your system (installed new packages or set different
env vars) then manually "rm -rf build" and try running "gradle"
again and see if that helps.
-- Kevin
https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-EnvironmentVariables Zitat von
Post by f***@swingempire.de
that is having downloaded, installed the required tools, added
env vars as desribed.
Then in cygwin, navigate to the git working dir, typing
gradle tasks
FAILURE: Build failed with an exception.
Script
92
A problem occurred evaluating script.
FAIL: WINSDK_DIR not defined
to me, it looks the env var WINSDK_DIR is not set - what should go in there?
Thanks, Jeanette
BTW: did I ever mention that I hate command line tools - and they
feel it, fighting back with all they got ;)
f***@swingempire.de
2018-10-31 14:58:43 UTC
Permalink
wasn't as bad as expected, just had to interrupt because it took ages
to test the webkit (which wasn't build so all its tests ran until each
timed out)
Task :web:test
*****************************************************
WARNING: running web tests without building webkit.
The webkit native library will be copied from the JDK,
which might lead to failures in some web tests.
To avoid these failures, you should either build
webkit locally, copy the native webkit library from a
recent build, or skip execution of web test cases with
'-x :web:test'
*****************************************************

fine to get informed after the fact <g> Hmm .. I would expect the default
script to behave the other way round: if the the webkit isn't built, then its
tests aren't run by default (but can be included if need be)

but well, I'm just starting to get my pants wet, so take whatever I expect
with a bag of salt :)

On another track: building everything from scratch takes some time - can I
use those build artefacts (namely the test infrastructure) and copy it over to
a single module project and just use it?

hmm .. need to try, tomorrow or so. Thanks so far!
okay after deleting the properties and running again, it at least
lists the tasks without error - thanks :)
now will try a real build - expecting all hell breaking loose <g>
Nir Lisker
2018-10-31 15:17:25 UTC
Permalink
Can I remove the step for "DirectX SDK June 2010"? I think it was already
verified that it's not needed.

- Nir
Post by f***@swingempire.de
wasn't as bad as expected, just had to interrupt because it took ages
to test the webkit (which wasn't build so all its tests ran until each
timed out)
Task :web:test
*****************************************************
WARNING: running web tests without building webkit.
The webkit native library will be copied from the JDK,
which might lead to failures in some web tests.
To avoid these failures, you should either build
webkit locally, copy the native webkit library from a
recent build, or skip execution of web test cases with
'-x :web:test'
*****************************************************
fine to get informed after the fact <g> Hmm .. I would expect the default
script to behave the other way round: if the the webkit isn't built, then its
tests aren't run by default (but can be included if need be)
but well, I'm just starting to get my pants wet, so take whatever I expect
with a bag of salt :)
On another track: building everything from scratch takes some time - can I
use those build artefacts (namely the test infrastructure) and copy it over to
a single module project and just use it?
hmm .. need to try, tomorrow or so. Thanks so far!
okay after deleting the properties and running again, it at least
lists the tasks without error - thanks :)
now will try a real build - expecting all hell breaking loose <g>
f***@swingempire.de
2018-10-31 15:26:33 UTC
Permalink
yes, I think so - don't have it and nothing barked at me
Post by Nir Lisker
Can I remove the step for "DirectX SDK June 2010"? I think it was already
verified that it's not needed.
- Nir
Post by f***@swingempire.de
wasn't as bad as expected, just had to interrupt because it took ages
to test the webkit (which wasn't build so all its tests ran until each
timed out)
Task :web:test
*****************************************************
WARNING: running web tests without building webkit.
The webkit native library will be copied from the JDK,
which might lead to failures in some web tests.
To avoid these failures, you should either build
webkit locally, copy the native webkit library from a
recent build, or skip execution of web test cases with
'-x :web:test'
*****************************************************
fine to get informed after the fact <g> Hmm .. I would expect the default
script to behave the other way round: if the the webkit isn't built, then its
tests aren't run by default (but can be included if need be)
but well, I'm just starting to get my pants wet, so take whatever I expect
with a bag of salt :)
On another track: building everything from scratch takes some time - can I
use those build artefacts (namely the test infrastructure) and copy it over to
a single module project and just use it?
hmm .. need to try, tomorrow or so. Thanks so far!
okay after deleting the properties and running again, it at least
lists the tasks without error - thanks :)
now will try a real build - expecting all hell breaking loose <g>
Kevin Rushforth
2018-10-31 16:08:30 UTC
Permalink
Make it so. :)

-- Kevin
Post by f***@swingempire.de
yes, I think so - don't have it and nothing barked at me
Post by Nir Lisker
Can I remove the step for "DirectX SDK June 2010"? I think it was already
verified that it's not needed.
- Nir
Post by f***@swingempire.de
wasn't as bad as expected, just had to interrupt because it took ages
to test the webkit (which wasn't build so all its tests ran until each
timed out)
Task :web:test
*****************************************************
WARNING: running web tests without building webkit.
The webkit native library will be copied from the JDK,
which might lead to failures in some web tests.
To avoid these failures, you should either build
webkit locally, copy the native webkit library from a
recent build, or skip execution of web test cases with
'-x :web:test'
*****************************************************
fine to get informed after the fact <g> Hmm .. I would expect the default
script to behave the other way round: if the the webkit isn't built,
then
its
tests aren't run by default (but can be included if need be)
but well, I'm just starting to get my pants wet, so take whatever I expect
with a bag of salt :)
On another track: building everything from scratch takes some time - can I
use those build artefacts (namely the test infrastructure) and copy it over to
a single module project and just use it?
hmm .. need to try, tomorrow or so. Thanks so far!
okay after deleting the properties and running again, it at least
lists the tasks without error - thanks :)
now will try a real build - expecting all hell breaking loose <g>
Michael Ennen
2018-11-01 22:06:18 UTC
Permalink
Also don't forget about the Windows build script:

https://github.com/javafxports/openjdk-jfx/blob/develop/tools/scripts/build.ps1

It is what I use to automate the process of building OpenJFX on Windows as
much as
possible. Any improvements to the script would be appreciated.
Post by f***@swingempire.de
https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-EnvironmentVariables
Post by f***@swingempire.de
that is having downloaded, installed the required tools, added env
vars as desribed.
Then in cygwin, navigate to the git working dir, typing
gradle tasks
FAILURE: Build failed with an exception.
Script
92
A problem occurred evaluating script.
FAIL: WINSDK_DIR not defined
to me, it looks the env var WINSDK_DIR is not set - what should go in
there?
Post by f***@swingempire.de
Thanks, Jeanette
BTW: did I ever mention that I hate command line tools - and they
feel it, fighting back with all they got ;)
--
Michael Ennen
Johan Vos
2018-11-02 18:56:32 UTC
Permalink
Hi Michael,

What environment do you use to run that Windows build script?
The windows builds are the ones I still feel least comfortable about. We
tried to automate those on AdoptOpenJDK infrastructure, but they are using
Ansible for provisioning machines (for very good reasons), and we spent
days trying to come up with an Ansible script that allowed to build on
Windows, without 100% success.
Hence, we currently create the windows build on a Windows machine with a
fixed setup. It would be better of course to move more of the environment
and context parameters to the build procedure itself, and your script seems
a step in that direction. But what infrastructure do you use to run this?

- Johan
Post by Michael Ennen
https://github.com/javafxports/openjdk-jfx/blob/develop/tools/scripts/build.ps1
It is what I use to automate the process of building OpenJFX on Windows as
much as
possible. Any improvements to the script would be appreciated.
https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-EnvironmentVariables
Post by f***@swingempire.de
Post by f***@swingempire.de
that is having downloaded, installed the required tools, added env
vars as desribed.
Then in cygwin, navigate to the git working dir, typing
gradle tasks
FAILURE: Build failed with an exception.
Script
'C:\Daten\data-for-work\eclipse\gitrep-openjdk\openjdk-jfx\buildSrc\win.gradle'
Post by f***@swingempire.de
Post by f***@swingempire.de
92
A problem occurred evaluating script.
FAIL: WINSDK_DIR not defined
to me, it looks the env var WINSDK_DIR is not set - what should go in
there?
Post by f***@swingempire.de
Thanks, Jeanette
BTW: did I ever mention that I hate command line tools - and they
feel it, fighting back with all they got ;)
--
Michael Ennen
Dean Wookey
2018-11-08 16:38:22 UTC
Permalink
Hi Johan,

Michael's build script helped me a lot. I'm on windows 10. It just runs in
powershell after installing chocolatey, (.\tools\scripts\build1.ps from the
openjdk root dir). The only environment variables I've got set are
JAVA_HOME/JDK_HOME. I did have to make some modifications however to
install the other dependencies and to handle the .dll's that weren't
packaged. Everything ran fine on my machine, but as soon as I tried using
the jars on another machine, I got linker errors. Below is the modified
version. It won't package the correct dlls if DebugNative is used though,
but as it is, it's working for me.

Dean

.\gradlew --stop
choco install ant
choco install vswhere
choco install zip
choco install visualstudio2017community
choco install visualstudio2017-workload-nativedesktop
choco install windows-sdk-7.1
choco install cygwin

$cygwinPath = (Get-ItemProperty -Path "HKLM:\SOFTWARE\Cygwin\setup").rootdir
$env:Path += ";$($cygwinPath)\bin"

$env:WINSDK_DIR = (Get-ItemProperty -Path
"HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows Kits\Installed
Roots").KitsRoot10
$env:VCINSTALLDIR = "$(vswhere -legacy -latest -property
installationPath)\VC\Auxiliary\Build"
$vcRoot = "$(vswhere -legacy -latest -property installationPath)"
$msvcToolsVer = Get-Content
"$env:VCINSTALLDIR\Microsoft.VCToolsVersion.default.txt"
$msvcRedistVer = Get-Content
"$env:VCINSTALLDIR\Microsoft.VCRedistVersion.default.txt"

if ([string]::IsNullOrWhitespace($msvcToolsVer)) {
# The MSVC tools version file can have txt *or* props extension.
$msvcToolsVer = Get-Content
"$env:VCINSTALLDIR\Microsoft.VCToolsVersion.default.props"
}
$env:MSVC_VER = $msvcToolsVer
$env:MSVC_REDIST_VER = $msvcRedistVer

$files = Get-ChildItem
"$($vcRoot)/VC/Redist/MSVC/$($msvcRedistVer)/x86/*.CRT/"
$crtVer = $files[0].Name.replace("Microsoft.VC","").replace(".CRT","")
$env:WINDOWS_CRT_VER = $crtVer


$env:VS150COMNTOOLS = $env:VCINSTALLDIR
$env:VSVARS32FILE = "$env:VCINSTALLDIR\vcvars32.bat"
refreshenv
if ($env:APPVEYOR -eq "true") {
.\gradlew all test -PCOMPILE_WEBKIT=false -PCONF=Debug --stacktrace -x
:web:test --info --no-daemon
if ($lastexitcode -ne 0) {
exit $lastexitcode
}
} else {
.\gradlew all test -PCOMPILE_WEBKIT=false -PCONF=Debug --stacktrace -x
:web:test --info
}
Post by Johan Vos
Hi Michael,
What environment do you use to run that Windows build script?
The windows builds are the ones I still feel least comfortable about. We
tried to automate those on AdoptOpenJDK infrastructure, but they are using
Ansible for provisioning machines (for very good reasons), and we spent
days trying to come up with an Ansible script that allowed to build on
Windows, without 100% success.
Hence, we currently create the windows build on a Windows machine with a
fixed setup. It would be better of course to move more of the environment
and context parameters to the build procedure itself, and your script seems
a step in that direction. But what infrastructure do you use to run this?
- Johan
https://github.com/javafxports/openjdk-jfx/blob/develop/tools/scripts/build.ps1
Post by Michael Ennen
It is what I use to automate the process of building OpenJFX on Windows
as
Post by Michael Ennen
much as
possible. Any improvements to the script would be appreciated.
https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-EnvironmentVariables
Post by Michael Ennen
Post by f***@swingempire.de
Post by f***@swingempire.de
that is having downloaded, installed the required tools, added env
vars as desribed.
Then in cygwin, navigate to the git working dir, typing
gradle tasks
FAILURE: Build failed with an exception.
Script
'C:\Daten\data-for-work\eclipse\gitrep-openjdk\openjdk-jfx\buildSrc\win.gradle'
Post by Michael Ennen
Post by f***@swingempire.de
Post by f***@swingempire.de
92
A problem occurred evaluating script.
FAIL: WINSDK_DIR not defined
to me, it looks the env var WINSDK_DIR is not set - what should go in
there?
Post by f***@swingempire.de
Thanks, Jeanette
BTW: did I ever mention that I hate command line tools - and they
feel it, fighting back with all they got ;)
--
Michael Ennen
Michael Ennen
2018-11-08 20:21:17 UTC
Permalink
Indeed it requires choco package manager and it is meant to be run in
powershell.

Thank you for taking the time to report what worked for you. If there are
any changes
you think should be added to the script, feel free to open a PR on
https://github.com/javafxports/openjdk-jfx
as it is now officially part of the GitHub repository. I sort of hacked it
together very quickly and
only tested it on my local dev machine so improvements are definitely
welcome.
Post by Dean Wookey
Hi Johan,
Michael's build script helped me a lot. I'm on windows 10. It just runs in
powershell after installing chocolatey, (.\tools\scripts\build1.ps from
the openjdk root dir). The only environment variables I've got set are
JAVA_HOME/JDK_HOME. I did have to make some modifications however to
install the other dependencies and to handle the .dll's that weren't
packaged. Everything ran fine on my machine, but as soon as I tried using
the jars on another machine, I got linker errors. Below is the modified
version. It won't package the correct dlls if DebugNative is used though,
but as it is, it's working for me.
Dean
.\gradlew --stop
choco install ant
choco install vswhere
choco install zip
choco install visualstudio2017community
choco install visualstudio2017-workload-nativedesktop
choco install windows-sdk-7.1
choco install cygwin
$cygwinPath = (Get-ItemProperty -Path
"HKLM:\SOFTWARE\Cygwin\setup").rootdir
$env:Path += ";$($cygwinPath)\bin"
$env:WINSDK_DIR = (Get-ItemProperty -Path
"HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows Kits\Installed
Roots").KitsRoot10
$env:VCINSTALLDIR = "$(vswhere -legacy -latest -property
installationPath)\VC\Auxiliary\Build"
$vcRoot = "$(vswhere -legacy -latest -property installationPath)"
$msvcToolsVer = Get-Content
"$env:VCINSTALLDIR\Microsoft.VCToolsVersion.default.txt"
$msvcRedistVer = Get-Content
"$env:VCINSTALLDIR\Microsoft.VCRedistVersion.default.txt"
if ([string]::IsNullOrWhitespace($msvcToolsVer)) {
# The MSVC tools version file can have txt *or* props extension.
$msvcToolsVer = Get-Content
"$env:VCINSTALLDIR\Microsoft.VCToolsVersion.default.props"
}
$env:MSVC_VER = $msvcToolsVer
$env:MSVC_REDIST_VER = $msvcRedistVer
$files = Get-ChildItem
"$($vcRoot)/VC/Redist/MSVC/$($msvcRedistVer)/x86/*.CRT/"
$crtVer = $files[0].Name.replace("Microsoft.VC","").replace(".CRT","")
$env:WINDOWS_CRT_VER = $crtVer
$env:VS150COMNTOOLS = $env:VCINSTALLDIR
$env:VSVARS32FILE = "$env:VCINSTALLDIR\vcvars32.bat"
refreshenv
if ($env:APPVEYOR -eq "true") {
.\gradlew all test -PCOMPILE_WEBKIT=false -PCONF=Debug --stacktrace -x
:web:test --info --no-daemon
if ($lastexitcode -ne 0) {
exit $lastexitcode
}
} else {
.\gradlew all test -PCOMPILE_WEBKIT=false -PCONF=Debug --stacktrace -x
:web:test --info
}
Post by Johan Vos
Hi Michael,
What environment do you use to run that Windows build script?
The windows builds are the ones I still feel least comfortable about. We
tried to automate those on AdoptOpenJDK infrastructure, but they are using
Ansible for provisioning machines (for very good reasons), and we spent
days trying to come up with an Ansible script that allowed to build on
Windows, without 100% success.
Hence, we currently create the windows build on a Windows machine with a
fixed setup. It would be better of course to move more of the environment
and context parameters to the build procedure itself, and your script seems
a step in that direction. But what infrastructure do you use to run this?
- Johan
https://github.com/javafxports/openjdk-jfx/blob/develop/tools/scripts/build.ps1
Post by Michael Ennen
It is what I use to automate the process of building OpenJFX on Windows
as
Post by Michael Ennen
much as
possible. Any improvements to the script would be appreciated.
https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-EnvironmentVariables
Post by Michael Ennen
Post by f***@swingempire.de
Post by f***@swingempire.de
that is having downloaded, installed the required tools, added env
vars as desribed.
Then in cygwin, navigate to the git working dir, typing
gradle tasks
FAILURE: Build failed with an exception.
Script
'C:\Daten\data-for-work\eclipse\gitrep-openjdk\openjdk-jfx\buildSrc\win.gradle'
Post by Michael Ennen
Post by f***@swingempire.de
Post by f***@swingempire.de
92
A problem occurred evaluating script.
FAIL: WINSDK_DIR not defined
to me, it looks the env var WINSDK_DIR is not set - what should go
in
Post by Michael Ennen
Post by f***@swingempire.de
there?
Post by f***@swingempire.de
Thanks, Jeanette
BTW: did I ever mention that I hate command line tools - and they
feel it, fighting back with all they got ;)
--
Michael Ennen
--
Michael Ennen
c***@bekwam.com
2018-10-31 15:22:26 UTC
Permalink
I've been pulling the latest and building successfully on Windows for the
past week. Here's a supplement to the official docs.



https://courses.bekwam.net/public_tutorials/bkcourse_building_openjfx_8_win.
html

-Carl
Johan Vos
2018-10-31 16:55:22 UTC
Permalink
Your site says these are for 8, but I assume it is very similar to 11? If
so, we should probably update the wiki with the instructions on your site.
Are there any particular parts of the wiki where you think corrections are
needed?
I think we should focus on 11 on the wiki, so it's really good you have
instructions for 8 on your site. But the 11 instructions on the wiki should
be working for everyone who wants to build 11.

- Johan
Post by c***@bekwam.com
I've been pulling the latest and building successfully on Windows for the
past week. Here's a supplement to the official docs.
https://courses.bekwam.net/public_tutorials/bkcourse_building_openjfx_8_win.
html
<https://courses.bekwam.net/public_tutorials/bkcourse_building_openjfx_8_win.html>
-Carl
Nir Lisker
2018-10-31 18:34:31 UTC
Permalink
Post by Johan Vos
I think we should focus on 11 on the wiki, so it's really good you have
instructions for 8 on your site. But the 11 instructions on the wiki should
be working for everyone who wants to build 11.
There are instructions for 8 on the wiki too, though I don't know if they
are correct.
As for 11, in the"Platform Prerequisites" section, I only updated the Win
instructions because that's what I have. Someone should look at Mac and
Linux.
Post by Johan Vos
Your site says these are for 8, but I assume it is very similar to 11? If
so, we should probably update the wiki with the instructions on your site.
Are there any particular parts of the wiki where you think corrections are
needed?
I think we should focus on 11 on the wiki, so it's really good you have
instructions for 8 on your site. But the 11 instructions on the wiki should
be working for everyone who wants to build 11.
- Johan
Post by c***@bekwam.com
I've been pulling the latest and building successfully on Windows for the
past week. Here's a supplement to the official docs.
https://courses.bekwam.net/public_tutorials/bkcourse_building_openjfx_8_win
.
Post by c***@bekwam.com
html
<
https://courses.bekwam.net/public_tutorials/bkcourse_building_openjfx_8_win.html
Post by c***@bekwam.com
-Carl
Johan Vos
2018-11-01 10:57:52 UTC
Permalink
Post by Johan Vos
I think we should focus on 11 on the wiki, so it's really good you have
Post by Johan Vos
instructions for 8 on your site. But the 11 instructions on the wiki should
be working for everyone who wants to build 11.
There are instructions for 8 on the wiki too, though I don't know if they
are correct.
As for 11, in the"Platform Prerequisites" section, I only updated the Win
instructions because that's what I have. Someone should look at Mac and
Linux.
Great, thanks for that. @Carl, can you confirm the instructions on the wiki
for 11 are correct? Or do you only build for 8?

Thanks,

- Johan
c***@bekwam.com
2018-11-01 12:33:35 UTC
Permalink
I’ve just been compiling 8 for Windows since I can get 11 from openjfx.io. I’m going to compile 8 for the Mac and Linux in the next week or two. I’ll post my notes again for these platforms.



-Carl



From: Johan Vos <***@gluonhq.com>
Sent: Thursday, November 1, 2018 6:58 AM
To: Nir Lisker <***@gmail.com>; Carl Walker <***@bekwam.com>
Cc: openjfx-***@openjdk.java.net Mailing <openjfx-***@openjdk.java.net>
Subject: Re: Problems building openjfx





On Wed, Oct 31, 2018 at 7:34 PM Nir Lisker <***@gmail.com <mailto:***@gmail.com> > wrote:

I think we should focus on 11 on the wiki, so it's really good you have
instructions for 8 on your site. But the 11 instructions on the wiki should
be working for everyone who wants to build 11.



There are instructions for 8 on the wiki too, though I don't know if they are correct.

As for 11, in the"Platform Prerequisites" section, I only updated the Win instructions because that's what I have. Someone should look at Mac and Linux.





Great, thanks for that. @Carl, can you confirm the instructions on the wiki for 11 are correct? Or do you only build for 8?



Thanks,



- Johan
Loading...