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 officia
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
i
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
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.
On Wed, Oct 31, 2018
Cc: openjfx-dev@openjdk.java.net Mailing
Subject: Re: Problems building openjfx
On Wed, Oct 31, 2018 at 7:34 PM Nir Lisker mailto:nlis...@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 inst
On Wed, Oct 31, 2018 at 7:34 PM Nir Lisker 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
>
> 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
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
Make it so. :)
-- Kevin
On 10/31/2018 8:26 AM, faste...@swingempire.de wrote:
yes, I think so - don't have it and nothing barked at me
Zitat von Nir Lisker :
Can I remove the step for "DirectX SDK June 2010"? I think it was
already
verified that it's not needed.
- Nir
On Wed, Oct 31, 201
yes, I think so - don't have it and nothing barked at me
Zitat von Nir Lisker :
Can I remove the step for "DirectX SDK June 2010"? I think it was already
verified that it's not needed.
- Nir
On Wed, Oct 31, 2018 at 4:59 PM wrote:
wasn't as bad as expected, just had to interrupt because it
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
Can I remove the step for "DirectX SDK June 2010"? I think it was already
verified that it's not needed.
- Nir
On Wed, Oct 31, 2018 at 4:59 PM wrote:
>
> 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 eac
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 nati
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
Zitat von faste...@swingempire.de:
thanks for the quick answer :)
hmm, those are nearly all empty:
WINDOWS_VS_DEVENV
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:/Prog
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 se
forgot the link to the instruction page, just in case there's another:
https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX#BuildingOpenJFX-EnvironmentVariables
Zitat von faste...@swingempire.de:
first try, following the instructions (for win10) at:
that is having downloaded, instal
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:\Date
18 matches
Mail list logo
