Framework support in Fire

[JohnMoshakis]

I was reading this thread

Importing frameworks in Oxygene for Cocoa

Exactly, that’s the problem. The current thinking is to zop the .framework up as part of the import. place that next to the .fx, so we can build and link. but the finished .app would be broken as soon as it gets back to Windows. Unless we cna somehow safely “flatten” the framework (ie drop the symlinks). But i’m not sure yet if that will be straight-forward, since there could be anything inside that framework folder, really, and we cant officially depend on its structure.

and it seems like the biggest problem is supporting it from windows. Would it be possible to just have it for Fire ?

I have been trying to make use of this

GitHub - wannabegeek/TFDatePicker: Enhanced Textual NSDatePicker, which has a...

I was able to get it building as a static library but the code is using NSBundle to store images and as far as I can tell you cant do that with a static library.

Cheers,
John

[steveflack]

@JohnMoshakis

and it seems like the biggest problem is supporting it from windows. Would it be possible to just have it for Fire ?

It would seem that Fire is adding things that aren’t in the VS product (such as .DSym generation - thanks for that one). I would be really happy to see Fire support Frameworks before the VS issues are worked around if need be. There’s 3rd party closed-source frameworks (Mac and iOS) that I will need to use in the final version of my project and currently no way of using them.

[jeremy]

Here is one I’d like to use (I haven’t attempted it yet, it’d just be a “nice to have” addition, when the main app is done).

itsbonczek/kingpin

[mh (marc hoffman)]

@jeremy

Here is one I’d like to use

Note that if you have source, you can of course always compile it into a static library in Xcode, and then use that.

@steveflack

It would seem that Fire is adding things that aren’t in the VS product (such as .DSym generation - thanks for that one).

.dSYM generation is in the core toolchain, it will work form VS too. it’s just that the option may not be exposed yet. (adding anew option to the UI is so much easier for Fire

Whatever solution we find for frameworks, it’ll need to work for VS and Fire, as both use the same toolchain.

Frameworks support really comes down to three things:

(a) using the “fake” frameworks that people used to build, pre iOS 8. These really are static libs, and i believe importing them should work with some FXGen magic.

(b) using real frameworks (iOS 8+ and OS X)

(c) building real frameworks (iOS 8+ and OS X)

[JohnMoshakis]

Has there been any progress ?

Sorry to keep asking about frameworks. The last 3 libraries I have tried have just come as frameworks and its a pain having to keep building as static libraries.
The last one I was going to use which was previously a static library have switched.

[mh (marc hoffman)]

Unfortunately not yet, sorry. 24 hours in the day and all that. I’ll make this a prio for the Defiant release (ie the one after the one we’re preparing now).