Thanks Danno, reading the patch now.

Richard

On Jun 29, 2013, at 8:01 AM, Danno Ferrin <danno.fer...@shemnon.com> wrote:

> Here's a patch that copies all the file types if variants are present, so now 
> all .a files show up in ios-sdk:
> 
> https://bitbucket.org/narya/jfx78/commits/e69d574206cf59ed25e215cfd2479c9aae2ab296
> 
> From my reading, .a files are static libraries, and dylib are dynamic 
> libraries.  iOS requires static linking if I read the docs correctly.
> 
> On Sat, Jun 29, 2013 at 1:17 AM, Richard Bair <richard.b...@oracle.com> wrote:
> I haven't been this low level on building iOS, so I'm not sure how this 
> works. On iOS we don't have dynamic libraries, so why does changing the name 
> of the dynamic libraries to be .a make a difference? Or are you really 
> looking for the .o files? What happens to those .a's?
> 
> I like the patch to push the dynamic library names into the .gradle files 
> (except it should be dylib instead of dynlib, right?)
> 
> Richard
> 
> On Jun 28, 2013, at 11:14 PM, Danno Ferrin <danno.fer...@shemnon.com> wrote:
> 
>> Here's a more general solution that pushes the naming into the compile 
>> target build files (not tried on all paths, but works for iOS)
>> 
>> https://bitbucket.org/narya/jfx78/commits/3a05c03810657d827d92d422fdadc3f2a60f9c62
>> 
>> On Fri, Jun 28, 2013 at 11:51 PM, Danno Ferrin <danno.fer...@shemnon.com> 
>> wrote:
>> 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
>> >>
>> >>
>> 
>> 
>> 
> 
> 

Reply via email to