XcodesApp
v2.4.1 - Now with 101% more login
Xcodesapp现在是XcodesOrg的一部分 - 在此处阅读更多
aria2 ，它最多使用16个连接来下载比Urlsession快3-5倍。xcode-select活动使版本活动。注意：iOS 18+，TVOS 18+，WatchOS 11+，Visionos 2+要求安装Xcode 16.1 Beta 3+活跃。
Xcodes支持几种语言的本地化。
由于以下社区用户，支持以下语言！
| 法语 ？？ | @dompepin | 意大利语?? | Gualtierofrigerio |
| 西班牙语 ？？？ | @cesartru88 | 韩国人 ？？ | @Ryan-Son |
| 俄语？ | @Alexmazlov | 土耳其语?? | @egesucu |
| 印地语?? | @kgurpreet | 中文模拟？ | @megabitsenmzq |
| 芬兰语?? | @marcusziade | 中文传统？ | @itszero |
| 乌克兰人?? | @gelosi | 日本人 ？？ | @tatsuz0u |
| 德语?? | @drct | 荷兰?? | @jfversluis |
| 巴西葡萄牙？ | @brunomunizaf | 抛光 ？？ | @jakex7 |
| 加泰罗尼亚 | @ferranabello | 希腊语?? | @Alladinian |
想添加更多语言吗？只需使用更新的字符串文件创建PR即可。
v1.x-需要macos 11或更新的v2.x-要求macos 13
开发人员ID签名和公证的发布版本可在Homebrew上提供。这些不需要已经安装XCode即可使用。
brew install --cask xcodesXcodes.app移动到/Applications目录Xcodes.App和CLI已更新，并与像您这样的贡献者进行维护。甚至开源库和工具都带有费用。如果您想支持Xcodes或捐赠该工具的开发和维护，这将不胜感激。绝对没有义务！
您需要MacOS 13.5 Ventura和Xcode 15才能构建和运行Xcodes.app。
Unxip和aria2必须作为通用二进制编译
# compile for Intel
swiftc -parse-as-library -O -target x86_64-apple-macos11 unxip.swift
# compile for M1
swiftc -parse-as-library -O -target arm64-apple-macos11 unxip.swift
# combine for universal binary
lipo -create -output unxip unxip_intel unxip_m1
# check it
lipo -archs unxip
著名的设计决策记录在决策中。 Apple身份验证流在Apple..paw中描述，这将使您可以使用PAW应用程序涉及的API端点。
xcode-install和Fastlane/SpaceShip都值得一提的是，弄清楚这使这是可能的困难部分。
请按照下面的步骤构建并发布新版本的Xcodes.app。对于任何GIT步骤，您可以使用首选工具，但请签署标签。
# Update the version number in Xcode and commit the change, if necessary
# Question: Did anything in XPCHelper change?
# - com.xcodesorg.xcodesapp.Helper folder and HelperXPCShared
# - if so, bump the version number in com.xcodesorg.xcodesapp.Helper target.
# Note: you do not have to bump the version number if nothing has changed.
# Note2: If you do bump the version, the end user, must re-install the XPCHelper and give permission again.
# Increment the build number
scripts/increment_build_number.sh
# Commit the change
git add Xcodes/Resources/Info.plist
git commit -asm " Increment build number "
# Tag the latest commit
# Replace $VERSION and $BUILD below with the latest real values
git tag -asm " v $VERSIONb$BUILD " " v $VERSIONb$BUILD "
# Push to origin
git push --follow-tags
# Build the app
# Make sure you have the Xcode Selected you want to build with
scripts/package_release.sh
# Notarize the app
# Do this from the Product directory so the app is zipped without being nested inside Product
# Create a app specific password on appleid.apple.com if you haven't already
# xcrun notarytool store-credentials "AC_PASSWORD"
# --apple-id "[email protected]"
# --team-id "teamid"
# --password "app specific password"
pushd Product
../scripts/notarize.sh Xcodes.zip < MYORG >
# Sign the .zip for Sparkle, note the signature in the output for later
# If you're warned about the signing key not being found, see the Xcodes 1Password vault for the key and installation instructions.
../scripts/sign_update Xcodes.zip
popd
# Go to https://github.com/XcodesOrg/XcodesApp/releases
# If there are uncategorized PRs, add the appropriate label and run the Release Drafter action manually
# Edit the latest draft release
# Set its tag to the tag you just pushed
# Set its title to a string with the format "$VERSION ($BUILD)"
# Polish the draft release notes, if necessary
# Add the signature to the bottom of the release notes in a comment, like:
< ! -- sparkle:edSignature= $SIGNATURE -- >
# Attach the zip that was created in the Product directory to the release
# Publish the release
shasum -a 256 xcodes.zip
# Update the [Homebrew Cask](https://github.com/XcodesOrg/homebrew-cask/blob/master/Casks/x/xcodes.rb). Matt Kiazyk- Twitter
Twitter | github | Mastadon |
