<div dir="ltr">Thanks for the reply Daniel. Your suggestion worked. Now I have to re-structure my whole project. :)<div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 23, 2016 at 8:23 PM, Daniel Dunbar <span dir="ltr"><<a href="mailto:daniel_dunbar@apple.com" target="_blank">daniel_dunbar@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Packages can have multiple executable targets. You just need to subdivide your sources appropriately:<br>
Sources/SomeLibrary/...<br>
Sources/server/main.swift<br>
Sourcers/upgrade-tool/main.swift<br>
...<br>
<br>
- Daniel<br>
<div><div class="h5"><br>
> On Jan 23, 2016, at 2:54 PM, Jason Lee via swift-users <<a href="mailto:swift-users@swift.org">swift-users@swift.org</a>> wrote:<br>
><br>
> Hi all,<br>
><br>
> I’m working on a server app and would like to be able to provide a utility executable to create certain things (source files) or do certain things (like migrate a database). My package only creates the one executable and for me to start another package - well, it seems like it would entail a lot more work than I want to do at this point (it’s so early in the dev stage).<br>
><br>
> Does anyone have any experience yet doing these sorts of things?<br>
><br>
> I was just thinking, I suppose my main could look for env parameters and doing my things if those are present or start the server if they are not. That might be the way to go.<br>
><br>
> Any thoughts appreciated, thanks.<br>
><br>
> - jason<br>
</div></div>> _______________________________________________<br>
> swift-users mailing list<br>
> <a href="mailto:swift-users@swift.org">swift-users@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-users" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-users</a><br>
<br>
</blockquote></div><br></div>