... and the second one is apparently overriding the first. It seems this
issue was noted on the swift-build-dev list several months ago: https://lists.swift.org/pipermail/swift-build-dev/
Week-of-Mon-20160919/000637.html
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?
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?
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?
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?
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.
···
On Tue, Jan 31, 2017 at 11:47 AM, Ankit Aggarwal <ankit_aggarwal@apple.com> wrote:
Hi,
Yep the ordering was fixed in this PR: Apple · GitHub
swift-package-manager/pull/715
SwiftPM will offer build settings in future to handle this properly.
On Tue, Jan 31, 2017 at 11:05 PM, Aaron Bohannon via swift-users < > swift-users@swift.org> wrote:
I am trying to compile code for macOS that depends on the AudioKit
framework.
This can be done using `swiftc`, as long as one passes the flag `-target
x86_64-apple-macosx10.11`.
So, in theory, it should be possible to use `swift build` by passing it
these flags:
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?
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?