build: introduce a CMake based build #70
Conversation
|
@swift-ci please test |
|
@swift-ci please test |
| #]] | ||
|
|
||
| add_library(SymbolKit | ||
| Mixin/Mixin+Equals.swift |
There was a problem hiding this comment.
I have similar concerns as I raised in swiftlang/swift-docc#818 (review) about the ongoing maintenance burden of this separate file list. It is slightly lessened in this repository because it doesn't get updated as frequently but I like if this was automatically kept up-to-date or at least if there was an easy way for another contributor to regenerate this file list based on find Sources/SymbolKit -type f -name "*.swift" | sort or something similar.
There was a problem hiding this comment.
That is effectively what the list is - but this should only be run on the CI as you may have other sources which are not yet included in the build in your local tree.
|
@swift-ci please test |
compnerd
force-pushed
the
cmake
branch
2 times, most recently
from
8b279c9 to
32f3dfc
Compare
This enables building DocC as a CMake project. Doing so is motivated by toolchain build times. By using CMake instead of SPM, we see an overall reduction of ~7% in the total toolchain build time on Windows.
|
@swift-ci please test |
2 participants
This enables building DocC as a CMake project. Doing so is motivated by toolchain build times. By using CMake instead of SPM, we see an overall reduction of ~7% in the total toolchain build time on Windows.