If I create a simple Xcode application (eg a SwiftUI app) and then import my Swift package as a dependency, then the resulting application can be profiled.
I noticed that none of the features in Xcode for doing build settings are available in pure Swift Packages, so perhaps that is why.
adrianm
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Hi Kacper, thanks for reply.
So running the above:
% codesign -dvvv --entitlements=- .build/arm64-apple-macosx/release/perftool
Executable=/Users/adrianm/Projects/soapybasic/SoapyBasicLib/.build/arm64-apple-macosx/release/perftool
Identifier=perftool
Format=Mach-O thin (arm64)
CodeDirectory v=20400 size=6561 flags=0x20002(adhoc,linker-signed) hashes=202+0 location=embedded
Hash type=sha256 size=32
CandidateCDHash sha256=dd4650a99e52e98e224350b0150293e990b96418
CandidateCDHashFull sha256=dd4650a99e52e98e224350b0150293e990b9641817aa23d58dad7899a62adc33
Hash choices=sha256
CMSDigest=dd4650a99e52e98e224350b0150293e990b9641817aa23d58dad7899a62adc33
CMSDigestType=2
CDHash=dd4650a99e52e98e224350b0150293e990b96418
Signature=adhoc
Info.plist=not bound
TeamIdentifier=not set
Sealed Resources=none
Internal requirements=none
I tested this on a simple Swift Xcode project and I get the entitlements in the plist and can Instrument the app.
But that's an app, not a package managed by Swift Package Manager.
Perhaps that is the key difference. Need to figure out how to sign a Swift Package?