[SR-18] OS X: provide error when 'swift/utils/build-script -l' uses unsupported configuration about llvm-project HOT 6 CLOSED

An alternative workaround is to use lldb/scripts/build-swift-cmake.py (use --help to see the options). But this only makes sense for Swift LLDB-focused developers. It is just a light wrapper around the Swift build-script, adding repository cloning/updating and other LLDB-centric options like including the system debugserver or including no debugserver on OS X builds.

from llvm-project.

swiftlang/swift@b08610b

from llvm-project.

Todd reverted this: swiftlang/swift@02a493b

from llvm-project.

I'm going to reimplement this, checking in build-script-impl so it catches any options passed to build-script that are intended for direct consumption by build-script-impl. In the case of build presets, we hit an issue where direct control of the lldb build variant was missed because it was not using the build-script mechanism to control build variant; rather, it was specifying the build-script-impl variant directly.

Something about that is a little icky; nonetheless, checking in build-script-impl is the most basic (and thorough) way to handle this.

from llvm-project.

SR-19 addresses the common RelWithDebInfoAsserts build variant that this issue here was meant to resolve.

I'll just make sure LLDB can build with the configurations that build-script can generate.

from llvm-project.

Not to be fixed. Rather, I'll be adding configurations we need.

from llvm-project.