macOS kernel needs to use real application name
See original GitHub issueNoting here from quick test: the macOS packaging succeeded last night after the fixes. However, the kernel doesn’t run in the packaged Slicer because there is no launcher. This line needs to be changed, because launcherExecutablePath
is empty string in a packaged build for macOS:
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Kernel extensions in macOS - Apple Support
User-Approved Kernel Extension Loading Starting with macOS 10.13. 2, users can use MDM to specify a list of kernel extensions that load without ......
Read more >XNU - Wikipedia
XNU is the computer operating system (OS) kernel developed at Apple Inc. since December 1996 for use in the Mac OS X (now...
Read more >Managing Legacy Kernel Extensions in macOS Using Jamf Pro
With macOS 11, additional steps are needed to load and use legacy kernel ... and then enter a Display Name and Kernel Extension...
Read more >Apple open-sourced the kernel of iOS and macOS for ARM ...
Apple open-sourced the kernel of iOS and macOS for ARM processors ... Apple has always shared the kernel of macOS after each major...
Read more >Mac kernel programming generic kernel extension prinf() not ...
you might have to look into console application and try putting your kernel extension name into the search textfield. all logs will be...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fixed by #10 (confirmed in 20180729 nightly on Mac)
Problem identified, fix on the way.