<div dir="ltr">Thanks. Using the latest Swift snapshot, I was able to get `swift build` to work on my code -- although I also had to hack the build script for the AudioKit framework so that I could recompile it with the latest Swift snapshot, too.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 31, 2017 at 11:47 AM, Ankit Aggarwal <span dir="ltr"><<a href="mailto:ankit_aggarwal@apple.com" target="_blank">ankit_aggarwal@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>Yep the ordering was fixed in this PR: <a href="https://github.com/apple/swift-package-manager/pull/715" target="_blank">https://github.com/apple/<wbr>swift-package-manager/pull/715</a></div><div>SwiftPM will offer build settings in future to handle this properly.</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Tue, Jan 31, 2017 at 11:05 PM, Aaron Bohannon via swift-users <span dir="ltr"><<a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">I am trying to compile code for macOS that depends on the AudioKit framework.<div><br></div><div>This can be done using `swiftc`, as long as one passes the flag `-target x86_64-apple-macosx10.11`.<br>
</div><div><br></div><div>So, in theory, it should be possible to use `swift build` by passing it these flags:</div><div><br></div><div> -Xswiftc -target -Xswiftc x86_64-apple-macosx10<wbr>.11</div><div><br></div><div>Unfortunately, `swift build` fails with this error:</div><div><br></div><div> error: module file's minimum deployment target is OS X v10.11</div><div><br></div><div>By passing `--verbose` to `swift build`, I learned that `swift build` is invoking `swiftc` with two copies of the `-target` flag:</div><div><br></div><div> -target x86_64-apple-macosx10.11 -target x86_64-apple-macosx10.10</div><div><br></div><div>... and the second one is apparently overriding the first. It seems this issue was noted on the swift-build-dev list several months ago: <a href="https://lists.swift.org/pipermail/swift-build-dev/Week-of-Mon-20160919/000637.html" target="_blank">https://lists.swift.org/piper<wbr>mail/swift-build-dev/Week-of-M<wbr>on-20160919/000637.html</a></div><div><br></div><div>I am running macOS 10.11 with Xcode 8.2.1. Has the bug been fixed in a development version of swift? If not, what work-around do you suggest?</div><div><br></div><div>Perhaps it would be simplest to recompile the AudioKit framework so that it has a minimum deployment target of macosx10.10? That project's scripts use xcodebuild to compile the framework, and they do not seem to explicitly specify a deployment target anywhere, but presumably this can be done by adding a line to the appropriate .xcconfig file. Does anyone know what line would need to be added?</div><span class="m_6251761888851064273HOEnZb"><font color="#888888"><div><br></div><div>- Aaron</div><div><br></div></font></span></div>
<br></div></div>______________________________<wbr>_________________<br>
swift-users mailing list<br>
<a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-users" rel="noreferrer" target="_blank">https://lists.swift.org/mailma<wbr>n/listinfo/swift-users</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>