So it looks like the first step is to set the COMPILE_TARGETS to include ios. However, the script it spits out .dynlib instead of .a files, just a naming thing.
Here's a fix it now patch: https://bitbucket.org/narya/jfx78/commits/1df1b31cb9618560551fb43cebe5dacb678f0c7f but a better patch would be to make a function in each platform build file. So this spits out some .a files if you know where to dig for them... gradle sdk -PCOMPILE_TARGETS=ios On Wed, Jun 26, 2013 at 10:45 AM, Richard Bair <richard.b...@oracle.com>wrote: > At the moment the first P0 is to make sure that when we switch to gradle > the rest of the development team is able to continue on with their work. It > is going to be bumpy for a few days, and we might miss the weekly > integration for example next week depending on how it goes. However I would > encourage anybody working on iOS to supply patches as soon as you have them > -- we're applying an Android patch today for instance. > > Richard > > On Jun 26, 2013, at 8:26 AM, Danno Ferrin <danno.fer...@shemnon.com> > wrote: > > > RoboVM + libs is the goal here, on iOS. The ant based libs worked > before. > > > > My brief read of the scripts indicates to me it is mostly a question of > > modifying some of the guard conditions in the build, but making it work > for > > the supported platforms first is more of a priority. > > > > On Wed, Jun 26, 2013 at 8:58 AM, Tobias Bley <t...@ultramixer.com> > wrote: > > > >> The problem is: a working gradle based iOS build isn’t of help to you > >> because you’ll have to statically compile the JDK and OpenJFX together > in > >> one library - maybe with Avian+OpenJDK or RoboVM (android based) + > OpenJFX. > >> > >> > >> Am 26.06.2013 um 03:41 schrieb Daniel Zwolenski <zon...@gmail.com>: > >> > >>> How do we go about building OpenJFX for iOS? Does it work now and/or > will > >>> the switch over to Gradle this friday/monday include support for an iOS > >>> build? > >>> > >>> I'll want to build from Danno's JFX78 backport but as I understand it, > he > >>> is hooking into the official gradle build scripts so one should > hopefully > >>> lead to the other. > >>> > >>> Cheers, > >>> Dan > >> > >> > >
