TheBrokenRail commented 4 years ago

Judging by https://github.com/darlinghq/darling/commit/9aad49fd6f6cb16587c0ef3af23abf249acc1b0e, the goal is to have a complete CLT builtin. Also according to #337, its a goal to have a working LLDB. Here are some ideas:

[x] Apple's cctools (otool, nm, etc) is already built, but not installed in /Library/Developer/DarlingCLT where xcrun expects it (fixed by darlinghq/darling-cctools#5)
[ ] LLDB
[ ] Git
[ ] xcode-select automatically downloads LLVM from https://releases.llvm.org/download.html
[ ] Install headers into the prefix (either directly into / or as an SDK within our CLT)

TheBrokenRail commented 4 years ago

ahyattdev commented 4 years ago

One way we could get Clang into our CLT is by downloading a prebuilt binary from here: https://releases.llvm.org/download.html

xcode-select could do this automatically when an install is requested.

This is of course dependent on #463.

I suggest this because clang is massive and building it our self wouldn't provide much benefit. We can also do the same for lldb and git.

ahyattdev commented 4 years ago

463 is nearing being fixed. This allows us to move forward with this.

The setup script can download our official working LLDB build, and then clang/git from the respective websites.

darlinghq / darling