<html><head><style>
body {
font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
padding:1em;
margin:auto;
background:#fefefe;
}
h1, h2, h3, h4, h5, h6 {
font-weight: bold;
}
h1 {
color: #000000;
font-size: 28pt;
}
h2 {
border-bottom: 1px solid #CCCCCC;
color: #000000;
font-size: 24px;
}
h3 {
font-size: 18px;
}
h4 {
font-size: 16px;
}
h5 {
font-size: 14px;
}
h6 {
color: #777777;
background-color: inherit;
font-size: 14px;
}
hr {
height: 0.2em;
border: 0;
color: #CCCCCC;
background-color: #CCCCCC;
display: inherit;
}
p, blockquote, ul, ol, dl, li, table, pre {
margin: 15px 0;
}
a, a:visited {
color: #4183C4;
background-color: inherit;
text-decoration: none;
}
#message {
border-radius: 6px;
border: 1px solid #ccc;
display:block;
width:100%;
height:60px;
margin:6px 0px;
}
button, #ws {
font-size: 12 pt;
padding: 4px 6px;
border-radius: 5px;
border: 1px solid #bbb;
background-color: #eee;
}
code, pre, #ws, #message {
font-family: Monaco;
font-size: 10pt;
border-radius: 3px;
background-color: #F8F8F8;
color: inherit;
}
code {
border: 1px solid #EAEAEA;
margin: 0 2px;
padding: 0 5px;
}
pre {
border: 1px solid #CCCCCC;
overflow: auto;
padding: 4px 8px;
}
pre > code {
border: 0;
margin: 0;
padding: 0;
}
#ws { background-color: #f8f8f8; }
.bloop_markdown table {
border-collapse: collapse;
font-family: Helvetica, arial, freesans, clean, sans-serif;
color: rgb(51, 51, 51);
font-size: 15px; line-height: 25px;
padding: 0; }
.bloop_markdown table tr {
border-top: 1px solid #cccccc;
background-color: white;
margin: 0;
padding: 0; }
.bloop_markdown table tr:nth-child(2n) {
background-color: #f8f8f8; }
.bloop_markdown table tr th {
font-weight: bold;
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr td {
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr th :first-child, table tr td :first-child {
margin-top: 0; }
.bloop_markdown table tr th :last-child, table tr td :last-child {
margin-bottom: 0; }
.bloop_markdown blockquote{
border-left: 4px solid #dddddd;
padding: 0 15px;
color: #777777; }
blockquote > :first-child {
margin-top: 0; }
blockquote > :last-child {
margin-bottom: 0; }
code, pre, #ws, #message {
word-break: normal;
word-wrap: normal;
}
hr {
display: inherit;
}
.bloop_markdown :first-child {
-webkit-margin-before: 0;
}
code, pre, #ws, #message {
font-family: Menlo, Consolas, Liberation Mono, Courier, monospace;
}
.send { color:#77bb77; }
.server { color:#7799bb; }
.error { color:#AA0000; }</style></head><body><p>Hello everyone,</p>
<p>Currently, we use <code>Package.swift</code> manifest file when defining our packages. Within the manifest file you define your targets, dependencies, excluded folders etc. This works fairly well while you’re using frameworks that exist on all supported platforms (ex. <code>Foundation</code>). </p>
<p>The main problem starts if you want to use code that exists only on macOS platform, for example, if you want to use Objective C runtime calls or UIKit. Then, you need to use bunch of <code>#if os(Linux)</code> to define what’s available on Linux and what’s available on macOS. While this approach can be non problematic for simple projects, it can introduce unnecessary complexity if you have a large target and dependency graph. </p>
<p>One way people tackle this problem is writing something like this:</p>
<pre><code class="swift">#if os(Linux)
let macOnlyTargets = []
#else
let macOnlyTargets = [
.Target(name: "SomeMacOSTarget")
]
#end
</code></pre>
<p>This structure looks even worse if you need to define more complex behaviors. For example, look at the <a href="https://github.com/ReactiveX/RxSwift/blob/master/Package.swift">RxSwift <code>Package.swift</code></a> file. In my case, I try to write <code>#if os(Linux)</code> as little as possible which leads me to writing my packages like:</p>
<pre><code class="swift">#if os(Linux)
// Define full Linux package
let package = Package(...)
#else
// Define full macOS package
let package = Package(..)
#end
</code></pre>
<h3 id="proposal">Proposal</h3>
<p>I propose that we support using different file for writing Linux package manifests. This file could be named:</p>
<ul>
<li><code>PackageLinux.swift</code></li>
<li><code>Package.Linux.swift</code></li>
<li><code>Package.linux.swift</code></li>
</ul>
<p>Inside this file you would be able to define your package only for Linux in the same way you’re defining one in regular <code>Package.swift</code>. The defined behaviors of building a package would be:</p>
<ol>
<li>If building on Linux and <code>PackageLinux.swift</code> is present, use that file when building the package.</li>
<li>If building on Linux and <code>PackageLinux.swift</code> is not present, use regular <code>Package.swift</code> manifest.</li>
<li>If building on macOS always use <code>Package.swift</code> manifest.</li>
</ol>
<h3 id="possibleproblems">Possible problems</h3>
<p>This behavior would only introduce problems when SPM gains support for new platforms, but then again, you would need to use new <code>#if os(somethingNew)</code> checks.</p>
<h3 id="compatibilitywithcurrentpackages">Compatibility with current packages</h3>
<p>This would be only a additive feature for Swift Package Manager and backwards compatibility will be maintained. </p></body></html>