I'm glad you're interested. We really should write progress report blog posts or something, similar to Dolphin emulator or RPCS3. Yes, the Xcode command line tools should work for the most part when running in Darling. If you try to use Darling for development please create issues on our GitHub if an individual tool crashes or otherwise fails to work.
Unfortunately, git doesn't work at the moment, however this can be worked around by using Linux git since Darling works in your Linux home folder.
One cool thing that works is lldb, which for the most part fully works.
Darling also supports mounting disk images and installing .pkgs, which is really helpful.
In short, we support most of what you can do from Terminal already.
Homebrew and MacPorts currently don't but once we get them working they should make it easier to install packages in a Darling prefix.
We also have binary compatibility with standard Mach-Os from macOS.
Unfortunately, the other project members (around four of us) and me are often busy with our lives and don't always have the time needed to advance Darling, so we are exploring how we can improve outreach to attract more developers.
While we are similar to the WINE project in goal, at the moment we have nowhere near the resources they do, so it is difficult to accomplish our goals.
> We really should write progress report blog posts or something, similar to Dolphin emulator or RPCS3.
Sure. I’m already pretty happy with the informational blog posts you have already; the linker one that was posted earlier this year was quite enlightening.
> we are exploring how we can improve outreach to attract more developers
No promises, but I might take a look sometime.I currently have easy access to macOS so I generally don’t have a good reason to run darling, but if I ever do and I run into a bug that annoys me I’ll see what I can do to help.
I'm quite interested in Darling, mostly for the purpose of cross-compiling from Linux -> Darwin. We cross-compile a lot of things for Julia, however cross-compiling executables that need to bootstrap something, (e.g. building something that then needs to run to generate output which is then used in further builds) can often get tricky. There are of course workarounds that can be utilized in order to get this to work (build a Linux-native version and a Darwin version, then use the Linux-native version of the software whenever a bootstrap is required) but this is tedious and not foolproof.
Unfortunately, git doesn't work at the moment, however this can be worked around by using Linux git since Darling works in your Linux home folder.
One cool thing that works is lldb, which for the most part fully works.
Darling also supports mounting disk images and installing .pkgs, which is really helpful.
In short, we support most of what you can do from Terminal already.
Homebrew and MacPorts currently don't but once we get them working they should make it easier to install packages in a Darling prefix.
We also have binary compatibility with standard Mach-Os from macOS.
Unfortunately, the other project members (around four of us) and me are often busy with our lives and don't always have the time needed to advance Darling, so we are exploring how we can improve outreach to attract more developers.
While we are similar to the WINE project in goal, at the moment we have nowhere near the resources they do, so it is difficult to accomplish our goals.