CMake based build #1720
CMake based build #1720
Conversation
|
@millenomi - the underlying CF changes that can be done are in a separate PR (that should go in first). The Foundation side of the changes I expect will require the CF to be built as a framework (which is part of what I did in the CMake based build). Once the base CF changes are in, I will rebase this. The hack for plutil I haven't figured out why the type of doesn't work. After that, I am going to try to switch over the Foundation build to CMake :-) |
|
With the CMake build, will |
|
@spevans, sure, passing |
compnerd
force-pushed
the
cmake-build
branch
2 times, most recently
from
2845f46
to
c77380b
Compare
compnerd
force-pushed
the
cmake-build
branch
5 times, most recently
from
79adb29
to
bcb1430
Compare
The CMake based build uncovered that swift can sometimes get confused about the refernece to type in the interpolation. Workaround it by specifying the qualified name. Thanks to Lily Vulcano for the hint!
This set of change is less than ideal. However, this is the last piece to make the generated toolchain image currently the same with the old build system. With this in plae, we can finally switch over to CMake.
|
Please test with following PRs: @swift-ci please test Linux platform |
These set of changes are needed to build with the CMake system.