Hello, The company I work for develops programming libraries for use on macOS systems. I'm able to build these libraries and code sign them, but I don't know how to notarize them. Our distribution mechanism is zip files downloaded from a customer-only website. Once downloaded the zip is just unzipped and it's ready to use. Is there a practical way to notarize zip files that contain compiled libraries instead of fully-fledged macOS applications? Namaste, John

Hello -I am new to MacOS kext development. From what I've read, it's important that the build ID for the OS in use and the KDK be in agreement. I'm assuming this is so that symbols line up, etc.I'm wondering about how to arrange this.The KDKs I see and can download for the release I'm starting with don't align with the build ID in the OS.For example, I'm working with 10.13.6 installed in a VMware VM. It's build ID is 17G9016. The closest build IDs in the list of KDKs that apply to 10.13.6 are 17G8030, 17G9007, and 17G9010.How do I get a 10.13.6 release that will have a build ID for which a corresponding KDK exists?Namaste,John

My client makes instrumentation that uses PCIe to do data transfers at high speed. Currently, the system can do 8GB / second sustained on Linux and Windows 10 systems. We'd like to develop the same capability for use on the new high-end Mac Pro systems. The client has a custom PCIe controller that works in existing PC architecture systems.As I understand it, DriverKit doesn't yet allow for the development of PCIe-based device drivers. My question is whether it is likely to be possible to do so in the future.