Contribute
Register

Compiling a .Kext for later versions of macOS

Status
Not open for further replies.
Joined
Nov 25, 2017
Messages
61
Motherboard
Toshiba Tecra Z50-C
CPU
i7-6600U
Graphics
HD 520
Mobile Phone
  1. Android
  2. iOS
  3. Other
I'm working through an issue that I found a likely solution for, found here:

Not all implementations of ACPI support quick-polling the way VirtualSMC uses it, and my laptop is one of them. RehabMan made a polling kext except it was written a while ago and when I import into Xcode, it won't compile for a variety of reasons.

I'm a C# developer so I get the code generally, but I have no idea what I'm doing in A: The macOS development environment, and B: in Xcode.

I was hoping someone might be able to take a quick look and see if there's a mostly simple solution to getting this to compile. Of course, using a pre-compiled .kext will halt the OS on boot since it's simply not written for things like Big Sur.

I've been trying to file an issue on Github for VirtualSMC to see if some of these methods can be implemented except from what I can tell, they have issues disabled on the public repo.

Is there any developers here interested in taking a look? It's not overly complicated code itself, but it's the environment dependencies I'm totally unfamiliar with that I can't work around.
 
If your issue is with VirtualSMC, you may try using FakeSMC instead.
 
If your issue is with VirtualSMC, you may try using FakeSMC instead.
I'm tempted to at least consider it yeah. It's not THAT big a deal breaker for me but might very well resolve the issue.
 
I've been trying to file an issue on Github for VirtualSMC to see if some of these methods can be implemented except from what I can tell, they have issues disabled on the public repo.

@Enigmahack,

Any issues or code change requests with Acidanthera kext's should be posted to the bugtracker project :-


This allows the developers to monitor just one page for all project issues rather than separate issue pages for each project which would be a nightmare to manage given the amount of projects they have active at any one time.

Cheers
Jay
 
Last edited:
@Enigmahack,

Any issues or code change requests with Acidanthera kext's should be posted to the bugtracker project :-


This allows the developers to monitor just one page for all project issues rather than separate issue pages for each project which would be a nightmare to manage given the amount of projects they have active at any one time.

Cheers
Jay

Ahhh, that actually makes more sense.

The problem right now is that I've read on acidanthera's several posts that they want solutions too. Just submitting a bug isn't enough. I'm trying to find that solution now, but can't compile their code in Xcode due to missing dependencies. That said, I will do really appreciate you providing their bugtracker issues page. It makes sense that they'd have 1 instead of one each.
 
The problem right now is that I've read on acidanthera's several posts that they want solutions too.

I don't think there is any problem with submitting an issue if it's something that would help improve a project, even if you don't have the full answer.

In your case the issue of VirtualSMC not supporting implementations of ACPI that do use quick-polling seems like a legitimate issue that I think should be brought to the attention of the developers.

If you do report it on the Bug Tracker then try to put as much information about the issue as possible, it's post's like "Such and Such does not work ... can you please fix it" that rattle them, rather than a detailed and well written description of the issue, hardware tested on, software versions .. etc.

Cheers
Jay
 
I don't think there is any problem with submitting an issue if it's something that would help improve a project, even if you don't have the full answer.

In your case the issue of VirtualSMC not supporting implementations of ACPI that do use quick-polling seems like a legitimate issue that I think should be brought to the attention of the developers.

If you do report it on the Bug Tracker then try to put as much information about the issue as possible, it's post's like "Such and Such does not work ... can you please fix it" that rattle them, rather than a detailed and well written description of the issue, hardware tested on, software versions .. etc.

Cheers
Jay
Thanks Jay - that actually makes sense.

It's definitely not an implementation or "I need help installing a .kext" issue, I've been working on this for almost a month now with no progress on my end.

I'll submit and include as much information as I can.
 
Ahhh, that actually makes more sense.

The problem right now is that I've read on acidanthera's several posts that they want solutions too. Just submitting a bug isn't enough. I'm trying to find that solution now, but can't compile their code in Xcode due to missing dependencies. That said, I will do really appreciate you providing their bugtracker issues page. It makes sense that they'd have 1 instead of one each.
Lilukext.kext it required for VirtualSMC.kext. Have you added that as a dependency?
 
Lilukext.kext it required for VirtualSMC.kext. Have you added that as a dependency?
Yes, absolutely.

It's other compiler dependencies that it seems to be missing that prevent it from compiling. I had to install a couple of header dependencies, the XNU SDK, but even still I'm getting errors when compiling like #Includes <Availability.h> missing, which leads me to believe even if I just 'copied the files' to get it to build, it's going to miss something else. I just don't know which package needs to be installed to fulfill all requirements.
 
Status
Not open for further replies.
Back
Top