Closed crystall1nedev closed 3 years ago
After a bit of weirdness with my first installation of Darling (I had to reset due to user error), I've got Darling working and am installing the command line tools for Xcode now. Let's hope that we won't need to install the full application for everything to work.
I noticed something about this though: Installing the SDKs. Darling, by default, installs MacOSX.sdk and MacOSX1013.sdk--so only the High Sierra and Catalina SDKs included with Darwin v19.6.0. We'll need to get the SDK from elsewhere, and a good place to start is at the xybp888/iOS-SDKs repository.
Xcode Command Line Tools installed.
iPhoneOS13.4.sdk installed.
Aaaand Homebrew won't install on Darling. Git keeps causing segmentation faults and then (potentially) corrupts your entire Darling prefix--not a good thing to have happen.
So time to manually install our dependencies.
Issues building cmake, I've been struggling with it for a while now.
I pretty much just used macosx in docker on arch Linux to build. https://github.com/sickcodes/Docker-OSX
That’s a good project and I’m glad that it works! I’m just looking for a way to do it without Docker or a virtual machine, and was originally intending to use Darling. However, I’m going to begin working on cross-compilation instead.
Closing this issue as neither route worked as easy as just setting up an OSX-KVM instance.
Take note that this isn't meant for anyone to follow just yet. This is simply me opening up a brainstorm platform as I experiment, and then report on my findings.
I'm starting to work with Darling on my Manjaro Linux PC to see if I can build PojavLauncher without needing anything other than this computer. This would be a step forward for people without Macs to be able to add their own contributions and not have to commit their changes to GitHub every time they want to build. Here's what I hope to accomplish:
xcode-select --select /Applications/Xcode.app