User Profile

I realize that kexts have been deprecated with Catalina, and we are working towards replacing them, but after upgrading to Xcode 11, I am no longer able to build and load my kext at all. With the exact same code and project (only difference is building with Xcode 11), I get the following error when trying to load my built kext:kxld[com.myorg.kext]: The super class vtable 'vtable for IOUserClient' for vtable 'vtable for com_myorg_kext_UserClient' is out of date. Make sure your kext has been built against the correct headers. kxld[com.myorg.kext]: The super class vtable 'vtable for IOService' for vtable 'vtable for com_myorg_kext' is out of date. Make sure your kext has been built against the correct headers.xld[com.myorg.kext]: The super class vtable 'vtable for IOService' for vtable 'vtable for com_myorg_kext' is out ofdIs there some way to be able to build the kext in Xcode 11, or do I just keep Xcode 10.3 around for the express purpose of building kexts?

I am working for a company (Company A) that was recently acquired by another company (Company B). We have a Developer ID certificate under both companies, and we are in the process of transitioning all our applications from Company A to Company B. Our Developer Program for Company A is set to expire in a couple of weeks, and we are wondering if we can continue to sign with Company A's Developer ID certificate for a couple of months after the developer program has lapsed. The Developer ID certificate doesn't expire until next year. The problem is that there are some release cycle constraints on our side (as well as some deployment constraints with some of our largest customers) that means one application will not be able to be fully-transitioned to be signed by Company B's Developer ID certificate prior to the expiration of Company A's developer program. We plan to do a final release update for that application within a couple of months - which needs to be signed with Company A's Developer ID, and after that point we can begin using Company B's Developer ID. So - the question is if we can let our Company A developer program expire (and use our Company B developer program for all DTS and certificate needs moving forward), but continue to sign our upcoming release with Company A's Developer ID certificate in a couple of months (after the developer program has expired, but before the certificate expires). Or, do we need to renew our Company A developer program for another year in order to continue using the Developer ID certificate in a couple of months?

Is there some kind of page describing details on how to build third-party open source libraries? In the platforms state of the union, it showed there were quite a few libraries already ported - is there some documentation on how to get access to build instructions for those (i.e. boost)? Alternatively, is there some kind of documentation as to how to modify a "standard" ./configure && make && make install workflow to just attempt at building an ARM64 build (I can do lipo after the fact to create the universal binary).