Skip to content
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

Binary frameworks are not copied to 'Build' folder when using Xcode 13.3 #3253

Open
mikchmie opened this issue Feb 1, 2022 · 7 comments · Fixed by Interfere/Utica#10 · May be fixed by #3254
Open

Binary frameworks are not copied to 'Build' folder when using Xcode 13.3 #3253

mikchmie opened this issue Feb 1, 2022 · 7 comments · Fixed by Interfere/Utica#10 · May be fixed by #3254

Comments

@mikchmie
Copy link

mikchmie commented Feb 1, 2022

  • carthage install method: [ ] .pkg, [x] homebrew, [x] source
  • which carthage: /usr/local/bin/carthage
  • carthage version: 0.38.0
  • xcodebuild -version: Xcode 13.3, Build version 13E5086k
  • Are you using --no-build? No
  • Are you using --no-use-binaries? No
  • Are you using --use-submodules? No
  • Are you using --cache-builds? No
  • Are you using --new-resolver? No
  • Are you using --use-xcframeworks? No

Cartfile

binary "https://dl.google.com/geosdk/GooglePlaces.json" == 6.0.0

Carthage Input

carthage bootstrap

Carthage Output

*** No Cartfile.resolved found, updating dependencies
*** Downloading binary-only framework GooglePlaces at "https://dl.google.com/geosdk/GooglePlaces.json"
*** xcodebuild output can be found in /var/folders/pq/n433_zn50fxbr6qm48hg2m_80000gq/T/carthage-xcodebuild.vsX42A.log
*** Downloading binary-only framework GooglePlaces at "https://dl.google.com/geosdk/GooglePlaces.json"

Actual outcome
Carthage did not copy binary framework GooglePlaces.framework to ./Carthage/Build/iOS/ folder.

Expected outcome
Carthage should copy all binary frameworks to ./Carthage/Build/<Platform>/ folders.

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Apr 16, 2022
@mikchmie
Copy link
Author

@up This issue is not stale. It's blocking the usage of Carthage with newest Xcode versions. PR with a fix is already waiting over 2 months for review.

@bitbytedog
Copy link

bitbytedog commented Apr 26, 2022

While waiting for the PR to be merged and a new release, the following workaround can be used:

sudo mv /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump.exe
cat << 'EOF' | sudo tee /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump
#!/bin/zsh
args=$(sed 's/[[:space:]][-]\([^-]\)/ --\1/g' <<<  " $@")
zsh -c "/usr/bin/xcrun objdump.exe $args"
EOF
sudo chmod a+x /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/objdump

It will convert single dash options to 2 dash options, and when the PR is merged and released, it will pass two dash options unchanged.

@iosdevben
Copy link

Would love to see this fixed ASAP.

@s-glagolev
Copy link

Hi, do we have any update with that issue?

@ozgur
Copy link

ozgur commented Jan 4, 2023

still the case in Xcode 14.1

@mikchmie
Copy link
Author

mikchmie commented Jan 30, 2023

Issue still occurs in newly released Carthage version 0.39.0. The PR that fixes it is still waiting for someone to review it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants