<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi Ricardo,</div><div class=""><br class=""></div><div class="">I'm not completely sure that I understand exactly what you're asking for, but generating Xcode projects and workspaces is really outside the scope of what the package manager does. Xcode is not part of the open source project. We are planning to build Swift Package Manager support into Xcode, so that might satisfy your needs here. That support is largely part of Xcode itself and not part of the open-source project, so we won't be discussing the details publicly until it's done.</div><div class=""><br class=""></div><div class="">I hope that helps,</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- Rick</div><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 22, 2015, at 5:53 PM, ricardo duarte via swift-build-dev <<a href="mailto:swift-build-dev@swift.org" class="">swift-build-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class="">Hi all,<br class=""><br class=""></div>First off all i am quite excited to see another tool to create package manager dependencies to come to the community.<br class=""><br class=""></div>After reading upon the existent examples i wonder if this tool will ever have the goal of allowing the generation of <span tabindex="-1" id=":17l.51" style="" class="">workspaces</span> and to link each project automatically, not only by pointing at binaries <span tabindex="-1" id=":17l.52" style="" class="">prebuilt</span> but at those in the derived-data, per example:<br class=""><br class=""></div><span tabindex="-1" id=":17l.53" style="" class="">MyWorkspace</span><br class=""></div>|---><span tabindex="-1" id=":17l.54" style="" class="">MyApp</span>.<span tabindex="-1" id=":17l.55" style="" class="">xcodeproj</span> (my app depends on MyFramework1 and MyFramework2<br class=""></div>| |--><span tabindex="-1" id=":17l.56" style="" class="">MyApp</span> (<span tabindex="-1" id=":17l.57" style="" class="">iOS</span> Target) which is linked to configurations (<span tabindex="-1" id=":17l.58" style="" class="">preproduction</span>/LIVE/etc)<br class="">| |--><span tabindex="-1" id=":17l.59" style="" class="">MyApp</span> (<span tabindex="-1" id=":17l.60" style="" class="">tvOS</span> Target) which is linked to configurations (<span tabindex="-1" id=":17l.61" style="" class="">preproduction</span>/LIVE/etc)<br class="">| |--><span tabindex="-1" id=":17l.62" style="" class="">MyApp</span> (<span tabindex="-1" id=":17l.63" style="" class="">macOS</span> Target) which is linked to configurations (<span tabindex="-1" id=":17l.64" style="" class="">preproduction</span>/LIVE/etc)<br class=""></div>|--->MyFramework1.<span tabindex="-1" id=":17l.65" style="" class="">xcodeproj</span><br class="">| |-->MyFramework1 ( <span tabindex="-1" id=":17l.66" style="" class="">iOS</span> Target) which is linked to configurations (<span tabindex="-1" id=":17l.67" style="" class="">preproduction</span>/LIVE/etc)<br class="">| |-->MyFramework1 (<span tabindex="-1" id=":17l.68" style="" class="">tvOS</span> Target) which is linked to configurations (<span tabindex="-1" id=":17l.69" style="" class="">preproduction</span>/LIVE/etc)<br class="">| |-->MyFramework1 (<span tabindex="-1" id=":17l.70" style="" class="">macOS</span> Target) which is linked to configurations (<span tabindex="-1" id=":17l.71" style="" class="">preproduction</span>/LIVE/etc)<br class="">|--->MyFramework2.<span tabindex="-1" id=":17l.72" style="" class="">xcodeproj</span><br class="">| |-->MyFramework2 (Target) which is linked to configurations (<span tabindex="-1" id=":17l.73" style="" class="">preproduction</span>/LIVE/etc)<br class="">| |-->MyFramework2 (<span tabindex="-1" id=":17l.74" style="" class="">tvOS</span> Target) which is linked to configurations (<span tabindex="-1" id=":17l.75" style="" class="">preproduction</span>/LIVE/etc)<br class="">| |-->MyFramework2 (<span tabindex="-1" id=":17l.76" style="" class="">macOS</span> Target) which is linked to configurations (<span tabindex="-1" id=":17l.77" style="" class="">preproduction</span>/LIVE/etc)<br class=""><br class=""></div>to allow the build with different configurations within <span tabindex="-1" id=":17l.78" style="" class="">Xcode</span> several schemes are created pointing at the same target with different <span tabindex="-1" id=":17l.79" style="" class="">preproduction</span>/post build scripts.<br class=""><br class=""></div>At the moment as my knowledge goes there is no such package manager within the community, and this setup is the currently the one used for our enterprise environment, I wonder if the community will ever be interested in allow such levels of customisation within the package manager itself, if other enterprise environments would benefit from it.<br class=""><br class="">There is quite an interest within my company and myself to have such tool, we wonder if the same interest exists within the community? <br class="">If that can be if nothing like this is in <span tabindex="-1" id=":17l.80" style="" class="">roadmap</span> is this a something that could be of use to wider population, and therefore would there be an interest create it? I would be very interested in my spare time to be part of the creation of such tool.<br class=""><br class=""></div>Regards<br class=""><br class=""></div>Ricardo<br class=""><div class=""><div class=""><br class=""><br class=""><div class=""><div class=""><br class=""></div></div></div></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=qz0eNO-2BnIaKwfHdqdSEoWDzK1gYoMlfMcRDuURe6g4nw8XMXd3W20XRbqLLHw0vR0eg-2BK7dl6V91SKwbIgKsoSlAnsKa9PDoc3YDjB8la-2BekdUN5AHp53mmU6qp32cWlLCJr-2Fn608BKgRZbPQ3L6VJufSd2s3t7QXlrBWAEnqAbcHZdGK5pGCHq2-2FblDRRe8JZyp5sLvhU1JVvTeOXdMSW4OP5uMG3xJ8bbrbJVvFEk-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
_______________________________________________<br class="">swift-build-dev mailing list<br class=""><a href="mailto:swift-build-dev@swift.org" class="">swift-build-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-build-dev<br class=""></div></blockquote></div><br class=""></body></html>