{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":239353303,"defaultBranch":"master","name":"Carthage","ownerLogin":"red1033","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2020-02-09T18:30:07.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/59042753?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1620670632.5254002","currentOid":""},"activityList":{"items":[{"before":"87fedfbcee0c64958bb0d74ce0447dd731d592ea","after":"cf0639251faf780d5214eb3227182302415bb13e","ref":"refs/heads/master","pushedAt":"2024-06-20T02:23:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"pull[bot]","name":null,"path":"/apps/pull","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/12910?s=80&v=4"},"commit":{"message":"[Untested, May Be Reverted] Due to Xcode 16.0 beta 1 — for `xcodebuild` — have Carthage pass `SUPPORTS_MACCATALYST=NO` just before `CARTHAGE=YES`.\n\nI would wager (even though Carthage can and will fix this easily) Apple may eventually deem this their Xcode Build Settings bug and fix this in a further Xcode 16 beta. The Build Setting under question is `EFFECTIVE_PLATFORM_NAME` containing `-maccatalyst` in an invocation like `xcodebuild -project \"/private/var/tmp/Alamofire5•9•1•••Carthage/Carthage/Checkouts/Alamofire/Alamofire.xcodeproj\" -scheme \"Alamofire iOS\" -configuration Release CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES build -showBuildSettings -skipUnavailableActions`.\n\nWe can fix this by — just prior to `CARTHAGE=YES` additionally having Carthage pass `SUPPORTS_MACCATALYST=NO` — which doesn't speak ‘universal truth’ about the framework we query, but does speak truth about how Carthage handles any framework or library. (Carthage always handle frameworks or libraries without attempting any maccatalyst builds.)\n\nWe consider adding that passed/hardcoded build setting safe — considering any likelihood ‘build setting chaining/interpolation’ using `SUPPORTS_MACCATALYST` is guessed to be almost entirely non-existent. But please chime in if unexpected downstream effects are seen (and file a new bug detailing which framework.)\n\nIf Apple fixes this in a further Xcode 16 beta, we may revert this.\n\n`brew uninstall carthage; brew install carthage --head` is a pathway that exists (attempt at one’s own discretion, and use the internet for associated prerun commands such as `brew uninstall` and others.)\n\n〜 As several CI providers no longer provide both ‘VNC access’ and Intel Mac builders, Carthage currently has no CI. Carthage maintainers shall be fixing this and commenting in the below link (and elsewhere.)\n\nFixes https://github.com/Carthage/Carthage/issues/3376.","shortMessageHtmlLink":"[Untested, May Be Reverted] Due to Xcode 16.0 beta 1 — for `xcodebuil…"}},{"before":"6ea08534cf3ca68ba5873ebcc080b4fc5968e098","after":"87fedfbcee0c64958bb0d74ce0447dd731d592ea","ref":"refs/heads/master","pushedAt":"2024-06-15T08:05:51.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"pull[bot]","name":null,"path":"/apps/pull","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/12910?s=80&v=4"},"commit":{"message":"[Untested, May Be Reverted] No longer (under Xcode 16 and above) prefix `-showBuildSettings` with solely the `archive` action. No longer (under Xcode 16 and above) leave `OBJROOT` as stands. Deal with error ‘Found no destinations for the scheme [^\\n]+ and action[…]’.\n\nNo longer (under Xcode 16 and above) prefix `-showBuildSettings` with solely the `archive` action. Carthage has long-standingly built `simulator` code under the `build` action, but (due to certain now-believed-to-be-fixed bugs, had historically passed the `archive` action when querying under simulator destinations for Xcode Build Settings.) Such a ‘discrepancy which Carthage relies upon improper values out of alignment with Xcode action verb,’ we now believe no longer works around any bugs and Xcode 16 (beta 1 (16A5171c) at the very least) now returns ‘proper’ Build Settings for simulator destinations and the `archive` action.\n\nXcode Build Setting `OBJROOT` now appears to have more path components. We lop some off (only under Xcode 16 and above.) Out of the three here, Carthage authors are most unsure about leaving this code change ‘as it stands.’ Especially under the purview of Carthage setting `--derived-data`. I’ll comment in the below link as actually running Carthages tests (unit and integration) should ‘prove out’ its sufficiency or deficit. PRs welcome.\n\nUnder all Xcode versions, all xcodebuild invocations of `-showBuildSettings` that return non-0 exit code and standardError matching `error[:] Found no destinations for the scheme [^\\n]+ and action [^\\n]+[.]\\n` will see non-surfacing of those errors. Carthage proceeds as if that xcodebuild invocation never happened (which is essentially how Carthage behaved before it had one more non-0 exit code return to deal with.)\n\n`brew install carthage --head` is a pathway that exists (attempt at one’s own discretion, and use the internet for associated prerun commands such as `brew uninstall` and others.)\n\n〜 As several CI providers no longer provide both ‘VNC access’ and Intel Mac builders, Carthage currently has no CI. Carthage maintainers shall be fixing this and commenting in the below link (and elsewhere.)\n\nPotentially fïxes https://github.com/Carthage/Carthage/issues/3375.\n\nPotentially fïxes https://github.com/Carthage/Carthage/issues/3374.\n\nSee https://github.com/Carthage/Carthage/issues/3374 for future updates on sufficiency of this commit, and whether lack of ‘may be reverted’ stands.","shortMessageHtmlLink":"[Untested, May Be Reverted] No longer (under Xcode 16 and above) pref…"}},{"before":"edf085cc652b9be8270720c21d2ca1b9fb12ff94","after":"6ea08534cf3ca68ba5873ebcc080b4fc5968e098","ref":"refs/heads/master","pushedAt":"2024-03-23T03:35:18.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"pull[bot]","name":null,"path":"/apps/pull","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/12910?s=80&v=4"},"commit":{"message":"Fix: 1 typo in MachHeader.swift\n\nSigned-off-by: RoboSchmied <github@roboschmie.de>","shortMessageHtmlLink":"Fix: 1 typo in MachHeader.swift"}},{"before":"0dc17e76612b605dfefeb6d2df5abebd1cc82ec2","after":"edf085cc652b9be8270720c21d2ca1b9fb12ff94","ref":"refs/heads/master","pushedAt":"2023-09-18T23:26:17.000Z","pushType":"push","commitsCount":13,"pusher":{"login":"pull[bot]","name":null,"path":"/apps/pull","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/12910?s=80&v=4"},"commit":{"message":"Bump version to 0.39.1","shortMessageHtmlLink":"Bump version to 0.39.1"}},{"before":"187a78c62811d3d75a9b1d41bfaeff708936125d","after":"0dc17e76612b605dfefeb6d2df5abebd1cc82ec2","ref":"refs/heads/master","pushedAt":"2023-09-11T20:26:37.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"pull[bot]","name":null,"path":"/apps/pull","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/12910?s=80&v=4"},"commit":{"message":"Fix Makefile to only pass `-static-stdlib` to `swiftc` when the old linker is `xcrun --find ld` returned.\n\nIf the new linker is there, then `dirname $(xcrun --find swift))/../lib/swift_static/macosx` should not be respected as the sentinel value it held in pre-«Xcode 15» days.\n\nIn the Makefile, we look for `'^only one snapshot supported'` (which only exists in the old linker) to tell us the old linker is present.\n\nSee <https://github.com/apple-opensource/ld64/blame/8568ce3517546665f1f9e0f7ba1858889a305454/src/ld/Snapshot.cpp> for the old linker.\nSee <https://github.com/apple-oss-distributions/dyld/> for the new linker.\n\nCloses <https://github.com/Carthage/Carthage/issues/3348>.","shortMessageHtmlLink":"Fix Makefile to only pass <code>-static-stdlib</code> to <code>swiftc</code> when the old l…"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEahQ1-QA","startCursor":null,"endCursor":null}},"title":"Activity · red1033/Carthage"}