When installing slicer_core on Mac in a new venv, it takes quite a while (about 2 minutes) to start it the first time, this is probably due to MacOS anti threat system.
This should be avoidable by signing the dylibs using something like this (warning: generated by AI):
codesign --force --options runtime --timestamp \
--sign "Developer ID Application: Your Name (TEAMID)" \
path/to/your_library.dylib....
xcrun notarytool submit wheel.whl \
--apple-id "your-email@example.com" \
--password "your-app-specific-password" \
--team-id "TEAMID" \
--waitKitware has signing servers, more info here: https://github.com/Slicer/Slicer/wiki/Signing-Application-Packages
When installing slicer_core on Mac in a new venv, it takes quite a while (about 2 minutes) to start it the first time, this is probably due to MacOS anti threat system.
This should be avoidable by signing the dylibs using something like this (warning: generated by AI):
codesign --force --options runtime --timestamp \ --sign "Developer ID Application: Your Name (TEAMID)" \ path/to/your_library.dylib.... xcrun notarytool submit wheel.whl \ --apple-id "your-email@example.com" \ --password "your-app-specific-password" \ --team-id "TEAMID" \ --waitKitware has signing servers, more info here: https://github.com/Slicer/Slicer/wiki/Signing-Application-Packages