What does “support” here mean? As far as I understand it, a package product is a static library, nothing more, so what prevents me from using it
to build a iOS or any other app?
What does “support” here mean? As far as I understand it, a package product is a static library, nothing more, so what prevents me from using it
to build a iOS or any other app?
Right, now we only compile for the host platform (OS X or Linux, currently). Among other things, we currently have no knowledge (or options to choose) what SDK or architecture you are targeting. We also have no mechanisms for specifying what platforms targets are compatible with in the manifest.
- Daniel
···
On Dec 4, 2015, at 4:36 PM, Dmitry Shevchenko <dmishe@me.com> wrote:
What does “support” here mean? As far as I understand it, a package product is a static library, nothing more, so what prevents me from using it
to build a iOS or any other app?
Right, now we only compile for the host platform (OS X or Linux, currently). Among other things, we currently have no knowledge (or options to choose) what SDK or architecture you are targeting. We also have no mechanisms for specifying what platforms targets are compatible with in the manifest.
Ah, sure, that makes sense.
Still, I do like the idea of having static libraries with Swift. Provided module name, this will allow for nice separation inside of my own projects.
Is there a timeline for having Xcode allow creating .a with Swift code inside? It seems that the compiler doesn’t mind, but Xcode is :)
···
On Dec 4, 2015, at 5:39 PM, Daniel Dunbar <daniel_dunbar@apple.com> wrote:
On Dec 4, 2015, at 4:36 PM, Dmitry Shevchenko <dmishe@me.com <mailto:dmishe@me.com>> wrote:
What does “support” here mean? As far as I understand it, a package product is a static library, nothing more, so what prevents me from using it
to build a iOS or any other app?
Right, now we only compile for the host platform (OS X or Linux, currently). Among other things, we currently have no knowledge (or options to choose) what SDK or architecture you are targeting. We also have no mechanisms for specifying what platforms targets are compatible with in the manifest.
Ah, sure, that makes sense.
Still, I do like the idea of having static libraries with Swift. Provided module name, this will allow for nice separation inside of my own projects.
Is there a timeline for having Xcode allow creating .a with Swift code inside? It seems that the compiler doesn’t mind, but Xcode is :)
For feature requests and comments about Xcode specifically, it is better to go through bugreporter.apple.com. We can't comment on specific features or timelines for unreleased products.
- Daniel
···
On Dec 5, 2015, at 7:42 PM, Dmitry Shevchenko <dmishe@me.com> wrote:
On Dec 4, 2015, at 5:39 PM, Daniel Dunbar <daniel_dunbar@apple.com <mailto:daniel_dunbar@apple.com>> wrote:
On Dec 4, 2015, at 4:36 PM, Dmitry Shevchenko <dmishe@me.com <mailto:dmishe@me.com>> wrote: