Git tag -asm "v $VERSIONb$BUILD " "v $VERSIONb$BUILD " # Push to origin Git commit -asm "Increment build number " # Tag the latest commit # Replace $VERSION and $BUILD below with the latest real values # Note2: If you do bump the version, the end user, must re-install the XPCHelper and give permission again. # Note: you do not have to bump the version number if nothing has changed. # Update the version number in Xcode and commit the change, if necessary # Question: Did anything in XPCHelper change? # - folder and HelperXPCShared # - if so, bump the version number in target. For any of the git steps, you can use your preferred tool, but please sign the tag. Releasing a new versionįollow the steps below to build and release a new version of Xcodes.app. Xcode-install and fastlane/spaceship both deserve credit for figuring out the hard parts of what makes this possible. The Apple authentication flow is described in Apple.paw, which will allow you to play with the API endpoints that are involved using the Paw app. Notable design decisions are recorded in DECISIONS.md. Lipo -create -output unxip unxip_intel unxip_m1 Swiftc -parse-as-library -O -target arm64-apple-macos11 unxip.swift Swiftc -parse-as-library -O -target x86_64-apple-macos11 unxip.swift Unxip and aria2 must be compiled as a universal binary # compile for Intel ![]() If you aren't a Robots and Pencils employee you'll need to change the CODE_SIGNING_SUBJECT_ORGANIZATIONAL_UNIT build setting to your Apple Developer team ID in order for code signing validation to succeed between the main app and the privileged helper. You'll need macOS 12 Big Sur and Xcode 13 in order to build and run Xcodes.app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |