You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 30, 2022. It is now read-only.
lets you run with the Xcode 12.2 beta 3 specified on Installation.md, as well as a normal Xcode 12 installation (not beta). Seems worth inserting one rpath so that people don't have to go find and install a new Xcode beta to try the toolchain.
Thanks for the workaround. I can confirm it works with 0.12 release (not RC) on macOS Big Sur 11.0.1, Xcode 12.2 (non-beta) and also Xcode 12.2 Beta 3.
I have noticed a tricky thing which could explain why some people couldn't reproduce the issue in #532. Xcode exhibits a different behavior for a SPM project (i.e. opening the Package.swift manifest) and Xcode project (obtained by running swift package generate-xcodeproj from the manifest).
Without the rpath fix above, an executable built from the SPM project works fine but the generated Xcode project fails to launch LLDB exactly as in #522.
It was happening to me with a Metal App, but I just had to change the Toolchain to the Xcode 12.2 default and it worked. I was using the " Swift for TensorFlow 0.12 release".
after all, sharing is caring... :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Same issue as 532.
The cause and solution are included here
(I pulled the link from @BradLarson 's pull request, I couldn't wait :) )
The text was updated successfully, but these errors were encountered: