-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xcodebuild
can't find the Half
module when building from the command line
#13
Comments
@toadzky What version of I just did a quick smoke test building a macOS app from the command line (after adding this lib as a Swift Package using Xcode's GUI) and don't see any issues. If using the latest version doesn't resolve your issue (or if you already are using the latest) are there any specific flags that you're passing to |
i was using 1.2.0. i switched it to master and it didn't help. i've also tried adding a direct dependency on half and that didn't work either. it almost seems like it's not building the dependencies in the right order. here's the output:
|
i was able to build a release in xcode by just using the |
unfortunately, xcode wouldn't embed the swift framework into the app, so i had to switch back to carthage and it won't build at all now. |
@toadzky I've been able to repro this issue and am at a loss as to the cause of it except that there appears to be an issue with the dependency build order when building through In the mean time, I've opened an issue with Apple about this: FB7622012. Hopefully they'll be able to address the issue in a future release of Xcode. |
Thanks, I shouldn't need half so I'll give 1.0.5 a try |
|
@toadzky There's a chance that some of the old references are still lingering around after downgrading versions. Try removing the following and trying again:
I whipped up a brand new Xcode project and added 1.0.5 as a dependency. Building this though Xcode and through xcodebuild works on my machine. I've seen similar issues to this while modifying Swift Package dependencies and doing the above steps normally resolves the issue. |
finally got it working. apparently there is some kind of issue with xcode copying the files correctly when based on scheme names. i wasn't explicitly specifying a scheme name to the i switched back to carthage and pinned to version 1.0.5 and it's building and running. |
@toadzky It happens to the best of us. I'll leave this open until I get something back from Apple regarding the bug that I opened about this issue. Also, after reading this I did a quick smoke test and I found that 1.2.0 builds and runs on my machine after adding the |
I'm not completely sure this is something that is the fault of this repo, but my app builds fine in Xcode itself, but my release script that automates several steps uses the
xcodebuild
command line and it fails with the following:I added it to my xcode project using xcode's gui for adding swift packages.
The text was updated successfully, but these errors were encountered: