<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>Swift, with its extension concept, is very well suited to modular development like this. We'd like to have a better option than frameworks to build reusable libraries. It's not an ABI thing, we really don't care about that, we use libs just to organize code, building them as a part of the app, and *not* to provide precompiled libraries to some other developers. Swift package manager does not work well within Xcode either at this time, and has a number of constraints we don't want (like having a separate git repo for each static lib -> that's not practical at all if you just have 1 or 2 files in that lib).</div></div></blockquote><div><br></div><div>You don't need to create one repo for each static library. A SwiftPM package consists of Modules. You can create any number of products consisting of one or more modules using the Product API in manifest file. for eg:</div><div><br></div><div><div>products += [Product(name: "StaticLibA", type: .Library(.Static), modules: "Foo"), Product(name: "StaticLibB", type: .Library(.Static), modules: "Foo", "Bar")]</div></div></div><div><br></div>-- <br><div class="gmail_signature">Ankit<br><br></div>
</div></div>