The life hack for this is to have a Run Script Build Phase that just lists out the build variables and their values. Then you look them up in the help menu to confirm what they mean.
> On Apr 26, 2020, at 10:29, Jack Brindle via Cocoa-dev > <cocoa-dev@lists.apple.com> wrote: > > Before someone reminds me, be sure to use the Xcode global variables for all > this work. You will find the build directory in one of the variables (it’s > Saturday - I don’t remember right now, so I hope someone bales me out again). > You can then use that var in the Notarization script to get your final > product. > > Once you get the hang of Notarization, you will find it isn’t difficult. > Getting there is, however. > > Jack > > >> On Apr 25, 2020, at 6:23 PM, Jack Brindle via Cocoa-dev >> <cocoa-dev@lists.apple.com> wrote: >> >> It seems like it would be easier to find the Build directory’s releases >> folder and the find the built product somewhere inside. It’s relation to the >> Build directory won’t change from build to build. Once you find that, just >> Notarize it in place. You need to make sure that it is already code/product >> signed (with hardened runtimes enabled). >> >> Sometimes doing things yourself is easier and simpler than having Xcode do >> it for you. >> >> Jack >> >> >>>> On Apr 25, 2020, at 10:05 AM, Gabriel Zachmann via Cocoa-dev >>>> <cocoa-dev@lists.apple.com> wrote: >>> >>> Thanks a lot for your response. >>> >>>> I’m not sure how you would script the export, but if you go to menu option >>>> Window -> Organizer, you can see your archives. >>> >>> Yes, I can see them. >>> But when I do "Show in Finder", then "Show package contents", they contain >>> nothing >>> (except for an empty Products folder, and an Info.plist). >>> >>>> From there you can export. Apps have the button “Distribute App”, and a >>>> command line program has the button “Distrubute Content”. >>> >>> Yes, screen savers have the “Distrubute Content” button, too. >>> >>>> Clicking that button lets you export the archive or the app/built >>>> products. Those are exported into a folder named with the date by default. >>> >>> Yes, but they contain just an empty "Products" folder. >>> >>> >>> Best regards, Gabriel >>> >>> >>> _______________________________________________ >>> >>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >>> >>> Please do not post admin requests or moderator comments to the list. >>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >>> >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/cocoa-dev/jackbrindle%40me.com >>> >>> This email sent to jackbrin...@me.com >> >> _______________________________________________ >> >> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) >> >> Please do not post admin requests or moderator comments to the list. >> Contact the moderators at cocoa-dev-admins(at)lists.apple.com >> >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/cocoa-dev/jackbrindle%40me.com >> >> This email sent to jackbrin...@me.com > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/dangerwillrobinsondanger%40gmail.com > > This email sent to dangerwillrobinsondan...@gmail.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
