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
Build phase - Build input files cannot be found #28
Comments
Hi Jules, You have to install it on your machine, either manually or via Mint as described here. The package is only for reading the generated file conveniently! Let me know if something is still unclear! |
Ah ok... I needed to added So the build phase now runs... but I don't seem to be getting any output. Any ideas ? Jules. |
Cool, did you add the file to your project/target as described in step 6 and 7? |
No I mean it didn't create a file. |
Oh hang on, I had the first checkout checked.... |
Hmm, what happens if you execute the command manually in your Terminal? I should generate it on your desktop. |
Yeah, it's in the path, so why doesn't it work when ran from the sh script Xcode creates. If I remove the if statement and just run the two lines, it fails with the same error. |
it runs fine from my home folder too... hmmm |
Xcode provides it's own environment and the PATH variable where the mint bin folder is added is not the one from your system... Both methods described in #27 should work, what happens when you try the second method where you create an alias to mint's swift-package-list with |
Awesome, working :) |
Awesome!! |
Hi,
I added the SPM, added the executable and the ui...
I assumed I didn't have to install (Aka using mint) as I used the SPM ?
Added the build phase and I'm getting this error...
error: Build input files cannot be found: '/Users/jm/Library/Developer/Xcode/DerivedData/Build/Products/Debug-iphoneos/ArgumentParser.o', '/Users/jm/Library/Developer/Xcode/DerivedData/Build/Products/Debug-iphoneos/ArgumentParserToolInfo.o' (in target 'swift-package-list' from project 'SwiftPackageList')
Any ideas ?
Thanks,
Jules.
The text was updated successfully, but these errors were encountered: