Re: Error on build

2017-12-03 Thread Michael Ennen
Try changing line 275 of the root build.gradle from: ext.IS_64 = OS_ARCH.toLowerCase().contains("64") to: ext.IS_64 = true On Sun, Oct 8, 2017 at 6:24 PM, wrote: > Hi, > > I possess an AMD 64 bit machine. > > My JDK_HOME points to a 64 bit JDK. > > MS C++

Re: Error on build

2017-10-08 Thread javafx
Hi, I possess an AMD 64 bit machine. My JDK_HOME points to a 64 bit JDK. MS C++ redistributables reported as installed on my machine (determined by control panel -> uninstall a program -> reviewing resulting list of installed sw) report both 32 and 64 installations. MS VS was installed as

Re: Error on build

2017-10-08 Thread David Bimamisa
Which version of JDK are you using? 64-bit or 32-bit? I remember getting these types of errors only if there was a mismatch between the JDK and c++ compiler machine type As noted in wiki: *"the version of the JDK you have set as JDK_HOME will determine whether you build 32 or 64 bit binaries"*

Re: Error on build

2017-10-06 Thread javafx
This is the result of using *VS 2017 CE- every option selected, downloaded and installed* I would say  there is an external symbol _fltused (float used?) and a few other such errors and also the assumption that the builder is on a 32 bit machine ?? (see final error). _fltused

Re: Error on build

2017-10-05 Thread David Bimamisa
Hi, I'm not sure whether DirectX is needed or not. So I stick with DirectX SDK (June 2010). But I think WINSDK is still needed since I got my build running only after installing Windows 10 SDK (shipped with visual studio 2017). However, I had to run the *vs_installer.ex*e again and go to "change"

Re: Error on build

2017-10-04 Thread Chris Newland
Thanks David. Do you know if the WINSDK and DirectX requirements are still as per the wiki/docs or can later versions be used? Cheers, Chris @chriswhocodes | JITWatch | DemoFX On Wed, October 4, 2017 13:15, David Bimamisa wrote: > It should also work with the community version of VS2017 > > >

Re: Error on build

2017-10-04 Thread David Bimamisa
It should also work with the community version of VS2017 Regards David Am 03.10.2017 5:56 nachm. schrieb : VS 2017 Professional is now required to build OpenJFX. > Ahh I see. I am sure it needs every bit of power offered by the professional version of Microsoft's

Re: Error on build

2017-10-03 Thread javafx
Kevin, Hey hi, nice to meet you.  Even given the exclusion of media and web, I don't think anyone is going to build it with VS 2010 EE edition, at least as the Gradle script is now.  I am *pretty sure*  I am following instructions to the letter, Is dotted Tees crossed.   The thing is I had

Re: Error on build

2017-10-03 Thread javafx
VS 2017 Professional is now required to build OpenJFX. Ahh I see. I am sure it needs every bit of power offered by the professional version of Microsoft's excellent dev environment but unfortunately it cuts me out of building or testing since I don't have that subscription and it's really

Re: Error on build

2017-10-03 Thread Kevin Rushforth
The Wiki is out of date. VS 2017 Professional is now required to build OpenJFX. A fix was just pushed [1] to allow a different build of VS 2017 than the hard-coded one. Also, I am still able to build with VS 2010 and VS 2013, which should work as long as you don't build media or webkit (they

Re: Error on build

2017-10-03 Thread javafx
Hi Chris, I am on Windows 7 and WinSDK 7.0A and DirectX June 10, 2010; not sure if any of that makes a difference here or not.  I cloned a couple weeks ago and in my win.gradle on line 68 it has a hard coded absolute path thus: defineProperty("WINDOWS_VS_VSINSTALLDIR", properties,

Re: Error on build

2017-10-03 Thread Chris Newland
Hi, I'm also trying to build OpenJFX on Windows 10 so I can add a Windows build to my community OpenJFX build server at https://chriswhocodes.com and am hitting the same problems as you. Setting WINSDK_DIR on the command line using 'set' or 'export' doesn't work and neither does setting via the

Re: Error on build

2017-10-02 Thread javafx
Hi again ! Well I was able to track down the source of the error I am receiving from the gradle build. Unfortunately, the error persists, which is a bit of a mystery. Maybe a gradle maven can enlighten me here. For some reason, this line on line 90-91 of win.gradle is throwing the