[SR-1738] add_swift_library takes SHARED/STATIC arg#3020
Conversation
a24c349 to
d2b273a
Compare
|
@swift-ci please test |
cmake/modules/AddSwift.cmake
Outdated
|
LGTM, but I wanted to ask you what is your long-term plan about |
|
@modocache OS X error: |
d2b273a to
dc0b754
Compare
|
@gribozavr Yes, that sounds like a good idea -- at some point I'll infer defaults based on I fixed the Intents SDK error -- my bad, I was working on an older branch, and on Linux. I also caught a new XPC SDK overlay was added (cool!), so I added the expansion to that call as well. Hopefully OS X tests will pass this time! |
f53588c to
2f18aa1
Compare
|
@swift-ci please test |
There was a problem hiding this comment.
@gribozavr You mentioned we always want libswiftRemoteMirror to be built as a shared library. Does this mean this should be hardcoded as SHARED, and only built when SWIFT_BUILD_STDLIB is turned on?
There was a problem hiding this comment.
Does this mean this should be hardcoded as
SHARED, and only built whenSWIFT_BUILD_STDLIBis turned on?
Yes to both, good catch!
As a first step to allowing the build script to build *only* static library versions of the stdlib, change `add_swift_library` such that callers must pass in `SHARED`, `STATIC`, or `OBJECT_LIBRARY`. Ideally, only these flags would be used to determine whether to build shared, static, or object libraries, but that is not currently the case -- `add_swift_library` also checks whether the library `IS_STDLIB` before performing certain additional actions. This will be cleaned up in a future commit.
2f18aa1 to
328de9e
Compare
|
@gribozavr Addressed the @swift-ci please test |
|
@modocache Thank you, merged! |
|
Awesome, thanks!! |
What's in this pull request?
As a first step to allowing the build script to build only static library versions of the stdlib (see #2431), change
add_swift_librarysuch that callers must pass inSHARED,STATIC, orOBJECT_LIBRARY.Ideally, only these flags would be used to determine whether to build shared, static, or object libraries, but that is not currently the case --
add_swift_libraryalso checks whether the libraryIS_STDLIBbefore performing certain additional actions. This will be cleaned up in a future commit./cc @gribozavr
ResolvedRelated bug number: (SR-1738)Before merging this pull request to apple/swift repository:
Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
Validation Testing
Lint Testing
Note: Only members of the Apple organization can trigger swift-ci.