KitwareMedical / KitwareMedical/SlicerCore
Slow first startup on Mac
Nobody has claimed this yet.
- Dominant language
- CMake
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
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" \
--wait
Kitware has signing servers, more info here: https://github.com/Slicer/Slicer/wiki/Signing-Application-Packages
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed codesign and xcrun notarytool commands, then read the Slicer signing servers guidance linked in the issue. Done means a fresh Mac virtual environment no longer takes about two minutes on its first startup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, macos
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100