<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">If you are only building application bundles for Darwin platforms, have no interest in server Swift, you don’t *need* to look into SPM for now. But as its going to be part of Xcode soon, and if you want to help shape into something you would be interested it, its always worth looking at it now.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 02 Aug 2016, at 14:24, zh ao <<a href="mailto:owenzx@gmail.com" class="">owenzx@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div class="">I have these questions because I saw SPM can build executables as well. I am wondering if I could benefit from learning SPM now or I should leave it alone.</div><div class=""><br class=""></div><div class="">It seems that those questions are too early to ask for one who is solely using Xcode.</div><div class=""><br class=""></div><div class="">Zhaoxin <br class=""><br class=""><div class="acompli_signature">Get <a href="https://aka.ms/o0ukef" class="">Outlook for iOS</a></div><br class=""></div><br class=""><br class=""><br class="">
<div class="gmail_quote">On Tue, Aug 2, 2016 at 8:15 PM +0800, "David Hart" <span dir="ltr" class=""><<a href="mailto:david@hartbit.com" target="_blank" class="">david@hartbit.com</a>></span> wrote:<br class="">
<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="3D"ltr"" class="">
<meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div class=""><div style="direction: inherit;" class="">I don't know what you mean by packaging. Xcode has been build responsibilities, including many which SPM does not currently address and may never will: building application bundles for Apple platforms, building resource bundles, building Darwin frameworks (I'm fairly sure SPM currently only builds simple libraries).</div><div style="direction: inherit;" class=""><br class=""></div><div style="direction: inherit;" class="">On the topic of what Xcode will become, this is not the place to discuss it. And I'm fairly sure you won't get any specifics from the Xcode team as it's still under Apple's umbrella of secrecy. The only thing we know or can guess is that it will get some sort of SPM integration.</div></div><div class=""><div style="direction: inherit;" class=""><br class=""></div>On 2 Aug 2016, at 13:54, Zhao Xin via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:georgia,serif">Is Swift Package Manager, SPM, the competitor to Xcode packaging? Or is it the future of Xcode packing? If it is, when will it be put into Xcode?</div><div class="gmail_default" style="font-family:georgia,serif"><br class=""></div><div class="gmail_default" style="font-family:georgia,serif">Also, what are the differences between built packages and Apple provided frameworks? Are they just the same thing with different names?</div><div class="gmail_default" style="font-family:georgia,serif"><br class=""></div><div class="gmail_default" style="font-family:georgia,serif">Zhaoxin</div></div>
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">swift-users mailing list</span><br class=""><span class=""><a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a></span><br class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-users" class="">https://lists.swift.org/mailman/listinfo/swift-users</a></span><br class=""></div></blockquote>
</div>
</blockquote>
</div>
</div></div></blockquote></div><br class=""></div></body></html>