You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

51 lines
2.0 KiB

  1. To sign, notarize, staple, and build the distribution DMG, you need to have
  2. an Apple Developer ID and a certificate. Once you have obtained these, proceed
  3. with the following:
  4. 1) Create a file in your home directory called ".tenacity_signing" and add
  5. the following three lines. Ensure you put in the email address you used
  6. for your Apple Developer account:
  7. NOTARIZE_USERNAME="specify your Apple developer email address"
  9. CODESIGN_APP_IDENTITY="Developer ID Application:"
  10. 2) You need to create an application specific password in your Developer
  11. account. Make sure you use "org.tenacityaudio.tenacity" as the app ID
  12. when following these instructions:
  14. 3) Now that you have the app password, use the following instructions to add
  15. that password to the keychain on your Mac:
  17. Use "TENACITY_PASSWORD" for the name as it must match the NOTARIZE_PASSWORD
  18. value above. Storing the password in your keychain protects it from curious
  19. eyes.
  20. 4) Build the Release version of Tenacity. You can follow the cmake_build.txt
  21. instructions in this folder. Once complete, you should find ""
  22. in:
  23. tenacity/bld/bin/Release
  24. 5) Open a terminal and change to the CMake build directory:
  25. tenacity/bld
  26. 6) Run this script to sign, notarize, staple and create the distribution DMG:
  27. ../mac/scripts/ ../mac bin/Release
  28. As it goes through the notarization process twice, once for the app bundle
  29. and again for the DMG, it will take awhile to run and you will see progress
  30. while waiting. If it is successful, you will find the Tenacity DMG in
  31. "tenacity/bld/bin" and you will receive an email confirming it was notarized.
  32. In the event of a failure, you will find a URL in the output messages
  33. displayed in the terminal. Paste that into a browser for information as
  34. to why it failed.