Re: Build fail: unresolved external symbol mainCRTStartup

2013-11-14 Thread Peter Zhelezniakov
> So, to build successfully, one can either install 64-bit JDK, > or change the build script for the two variables to match. > I tried the both approaches, the both worked. The real fix would be to pass OS_ARCH into the Qmake script somehow. Maybe using an environment variable?

Re: Build fail: unresolved external symbol mainCRTStartup

2013-11-14 Thread Leonid Popov
As Kevin reasonable noted, the problem was that 32-bit and 64-bit parts were mixed up. I checked the build scripts and found that there were two ways of getting the platform architecture there: 1. ext.OS_ARCH = System.getProperty("os.arch") in build.gradle 2. procarch = $$(PROCESSOR_ARCHITECTUR

Re: Build fail: unresolved external symbol mainCRTStartup

2013-11-13 Thread Stephen F Northover
Ok, you can't say that and not tell us what the problem was! Steve On 2013-11-13 9:55 AM, Leonid Popov wrote: Finally managed to build it with JDK 1.8-ea build 114 64 bit. On 11/12/2013 6:00 PM, Leonid Popov wrote: Thanks Kevin, but unfortunately it didn't help. Even having it cleaned complet

Re: Build fail: unresolved external symbol mainCRTStartup

2013-11-13 Thread Leonid Popov
Finally managed to build it with JDK 1.8-ea build 114 64 bit. On 11/12/2013 6:00 PM, Leonid Popov wrote: Thanks Kevin, but unfortunately it didn't help. Even having it cleaned completely, the build script still generates 32-bit YarrInterpreter.obj and then fails to link it to a 64-bit library.

Re: Build fail: unresolved external symbol mainCRTStartup

2013-11-12 Thread Anthony Petrov
Hi Leonid, I've never been able to build WebKit on my Windows in the past, so I don't know what the problem is. However, could you check what exactly the lib.exe is trying to link? Is it possible to enable some logging for nmake when building JavaScriptCoreJava, so that we actually see the co

Re: Build fail: unresolved external symbol mainCRTStartup

2013-11-12 Thread Leonid Popov
Thanks Kevin, but unfortunately it didn't help. Even having it cleaned completely, the build script still generates 32-bit YarrInterpreter.obj and then fails to link it to a 64-bit library. Still investigating. On 11/11/2013 8:43 PM, Kevin Rushforth wrote: Hi Leonid, Building JavaFX on Window

Re: Build fail: unresolved external symbol mainCRTStartup

2013-11-11 Thread Kevin Rushforth
Hi Leonid, Building JavaFX on Windows requires Cygwin, so it doesn't surprise me that it fails with a DOS shell. The error you are seeing on cygwin seems like a mismatch where part of the build is trying to use a 32-bit build and part trying to use 64-bit. My recommendation is to try the fo

Re: Build fail: unresolved external symbol mainCRTStartup

2013-11-11 Thread Leonid Popov
Hi Steve, Yes, I use 32-bit JDK for building. I tried to build it from both Windows and Cygwin command shells. The error I mentioned happens when building from Windows. If I try to build it from Cygwin, I get another error: Building Webkit configuration /Release/ into C:\javafx\8my\jfx\rt\m

Re: Build fail: unresolved external symbol mainCRTStartup

2013-11-08 Thread Chien Yang
Hi Leonid, I have no problem doing 32 bit build on my Windows 7 laptop though I haven't done a 64 bit build since we switched to gralde. Here is information about my gradle environment just in case it is helpful: $ gradle -v Grad

Re: Build fail: unresolved external symbol mainCRTStartup

2013-11-08 Thread Stephen F Northover
Hi Leonid, I have the same configuration as you I think. I'm just making sure I can build. First, do you have 32-bit JDK8? Are you running under a cygwin shell? What is your gradle command line? Steve On 2013-11-08 9:08 AM, Leonid Popov wrote: Hi, I've just cloned a new workspace from