Gradle build progress
Ali Ebrahimi
ali.ebrahimi1781 at gmail.com
Tue Apr 9 13:00:14 PDT 2013
HI Richard,
This is second part of patch.
diff -r 65f9877c4557 build-src/genVSproperties.bat
--- a/build-src/genVSproperties.bat Thu Mar 14 10:18:55 2013 -0400
+++ b/build-src/genVSproperties.bat Wed Apr 10 00:12:58 2013 +0430
@@ -81,6 +81,7 @@
echo windows.vs.LIB=%LIB%@@ENDOFLINE@@
echo windows.vs.LIBPATH=%LIBPATH%@@ENDOFLINE@@
echo windows.vs.PATH=%PATH%@@ENDOFLINE@@
echo windows.vs.VER=%VSVER%@@ENDOFLINE@@
+echo WINDOWS_SDK_DIR=%WindowsSdkDir%@@ENDOFLINE@@
echo ############################################################
Ali Ebrahimi
On Tue, Apr 2, 2013 at 7:51 PM, Richard Bair <richard.bair at oracle.com>wrote:
> Hi Ali,
>
> I will apply. Thanks for the patch!
>
> Richard
>
> On Mar 30, 2013, at 4:37 AM, Ali Ebrahimi <ali.ebrahimi1781 at gmail.com>
> wrote:
>
> Hi,
> I just provide patch for getting Win Sdk dir from system variable:
>
> diff -r 28fd91194a80 win.gradle
> --- a/win.gradle Fri Mar 29 17:06:43 2013 -0700
> +++ b/win.gradle Sat Mar 30 15:54:08 2013 +0430
> @@ -71,7 +71,7 @@
> windows_tools_stream = new FileInputStream(windows_tools);
> windows_tools_properties.load(windows_tools_stream);
> defineProperty("WINDOWS_VS_VSINSTALLDIR", windows_tools_properties,
> "absolute garbage");
> - defineProperty("WINDOWS_SDK_DIR", windows_tools_properties,
> "C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A")
> + defineProperty("WINDOWS_SDK_DIR", windows_tools_properties,
> System.getenv().get("WindowsSdkDir"))
> defineProperty("WINDOWS_VS_VCINSTALLDIR", windows_tools_properties,
> "$WINDOWS_VS_VSINSTALLDIR/VC")
> defineProperty("WINDOWS_VS_DEVENVDIR", windows_tools_properties,
> "$WINDOWS_VS_VSINSTALLDIR/Common7/IDE")
> defineProperty("WINDOWS_VS_DEVENVCMD", windows_tools_properties,
> "$WINDOWS_VS_DEVENVDIR/VCExpress.exe")
>
>
> Ali Ebrahimi
>
>
>
> On Wed, Mar 20, 2013 at 10:25 PM, Richard Bair <richard.bair at oracle.com>wrote:
>
>> I think the gradle scripts are now far enough along that you ought to be
>> able to successfully build using them on Mac, Linux, or Windows. At least,
>> I've managed to build on all three platforms but no doubt there are bugs on
>> various platforms due to different configurations.
>>
>> To try out the gradle scripts, get the latest graphics repo (
>> http://hg.openjdk.java.net/openjfx/8/graphics,
>> http://hg.openjdk.java.net/openjfx/8/graphics/rt).
>>
>> cd rt
>> gradle -b generator.gradle
>> cd ../javafx
>> gradle sdk
>>
>> You need to have gradle 1.4 installed on your system (I can't use gradlew
>> for now because including a 3rd party library in our source repository
>> requires legal review blah blah). I haven't tried it with other versions of
>> Gradle.
>>
>> It should successfully build all Java & native code, and successfully
>> download antlr, junit, and swt dependencies. It requires that
>> artifacts/sdk/rt/lib/ext/jfxrt.jar is present in your root graphics dir
>> just the same as the normal build, OR you can specify
>> -PBINARY_STUB=/path/to/latest/binary/stub/jfxrt.jar
>>
>> Please give it a try and let me know if it works for you or if it fails.
>>
>> I've also run apps based on the resulting libraries. Note that the JDK 8
>> builds have jfxrt.jar and associated native libraries on the ext class
>> path, which means when you run an app you will likely run into a mismatch
>> of native libraries or java source files. What I did was to remove
>> jfxrt.jar and the prism, prism-sw, decora-sse, and glass dylibs *out* of
>> my Java 8 JDK and supplied my gradle-built jfxrt.jar first on the class
>> path followed by the binary stub (old jfxrt.jar) file.
>>
>> Its a pain in the neck, I know. You can also mess with the ext class path
>> / boot class path settings, but that's a pain too. The joys of JDK
>> development :-/. Open to better suggestions on how to run locally built
>> jfxrt.jar and native libraries against a stock Java 8 without all the muss
>> & fuss.
>>
>> My next tasks:
>> - confirm javadoc generation works
>> - fix any failing tests or configuration that causes tests to fail
>> - specifically I'm working to get most tests to run
>> reliably in a single VM as they then execute 10x-100x faster
>> - jardiff the jfxrt.jar normally built with the one built by
>> gradle to look for bugs in the build script
>> - fix any build issues reported on this thread
>> - IDE integration
>>
>> Then I will work with Mong to get the release engineering requirements in
>> place and get a build setup on hudson and make sure all that is working
>> fine.
>>
>> Richard
>
>
>
>
More information about the openjfx-dev
mailing list