Thomas, It is definitely not too late. The push that Gary did was to our mobile/dev forest which is not the final forest before integration into OpenJDK. We pushed this to mobile/dev in order to allow interested developers to begin working with these changes and to provide us with feedback.
The final changesets will end up going to mobile/jdk9. This is the staging forest that we will eventually integrate into the mainline OpenJDK sources. Bob. > On Dec 18, 2015, at 9:17 PM, Thomas Stüfe <thomas.stu...@gmail.com> wrote: > > Hi Bob and Gary, > > Thank you for correcting this! Respect also on this large porting effort, > this looks like a lot of work and I am curious how this will turn out. > > I took a short look at your changes - especially the android-related changes > - and have a number of further questions and suggestions . I hope that this > is okay and the door is not already closed. > > I'm away from any computer however (ironically typing this from an android > device, so anything weird is due to auto correct :), so before Monday I will > not be able to do anything. > > I also think that this may be interesting to hotspot-runtime, because the > changes to the OS layer are somewhat extensive, so I'll take the freedom and > put them on the recipient list. > > Kind regards, Thomas > > On Dec 18, 2015 22:16, "Bob Vandette" <bob.vande...@oracle.com > <mailto:bob.vande...@oracle.com>> wrote: > I caught that and gave Gary an updated set of os_linux* files that hopefully > corrected this. > > Here’s the updated changes that Gary just pushed today. > > http://hg.openjdk.java.net/mobile/dev/hotspot/rev/f1acc8fa34b8 > <http://hg.openjdk.java.net/mobile/dev/hotspot/rev/f1acc8fa34b8> > > > Bob. > > > On Dec 18, 2015, at 4:11 PM, Thomas Stüfe <thomas.stu...@gmail.com > > <mailto:thomas.stu...@gmail.com>> wrote: > > > > Hi Gary, > > > > In the Linux os layer - especially in os_linux.cpp - I see you have > > reintroduced old coding we just painstakingly removed because it was not > > needed for modern Linuxes anymore. For instance, coding dealing with old > > Linuxthreads (vs Nptl, which is ubiquitous nowadays) or workarounds for old > > glibc bugs. Is this really needed for Android? Or is this just a merge > > error? > > > > Kind regards, Thomas > > On Dec 11, 2015 16:15, "Gary Adams" <gary.ad...@oracle.com > > <mailto:gary.ad...@oracle.com>> wrote: > > > >> Here's the initial upload of changes that provides support for the ios and > >> android ports > >> for the mobile/dev repos. While there have been some preliminary reviews > >> of the code, > >> there is still more work required before we will look for more thorough > >> reviews > >> and an integration to mobile/jdk9 repos. > >> > >> Issue: https://bugs.openjdk.java.net/browse/JDK-8145132 > >> <https://bugs.openjdk.java.net/browse/JDK-8145132> > >> Webrev: http://cr.openjdk.java.net/~gadams/8145132/webrev.00/ > >> <http://cr.openjdk.java.net/~gadams/8145132/webrev.00/> > >> > >> > >> Here's a simple configure script to generate a ios-x86_64 build for use > >> with the iphone simulator. (uses homebrew 64 bit freetype from pkgconfig) > >> > >> export JAVA_HOME=`/usr/libexec/java_home -v 1.8` > >> export PATH=$JAVA_HOME/bin:~/homebrew/bin:$PATH > >> > >> bash ../../configure \ > >> --openjdk-target=x86_64-macos-ios \ > >> --with-boot-jdk=$JAVA_HOME \ > >> --disable-warnings-as-errors \ > >> --disable-headful \ > >> --enable-static-build=yes \ > >> --with-jvm-variants=minimal1 > >> > >> > >> Also, tested with i586-macos-ios target for 32 bit > >> with a locally built --with-freetype 2.6.2. > >> >
