New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SR-1738] add_swift_library takes SHARED/STATIC arg #3020
[SR-1738] add_swift_library takes SHARED/STATIC arg #3020
Conversation
a24c349
to
d2b273a
Compare
@swift-ci please test |
@@ -473,6 +477,11 @@ function(_add_swift_library_single target name) | |||
if("${SWIFTLIB_SINGLE_INSTALL_IN_COMPONENT}" STREQUAL "") | |||
message(FATAL_ERROR "INSTALL_IN_COMPONENT is required") | |||
endif() | |||
|
|||
if(NOT SWIFTLIB_SINGLE_SHARED AND NOT SWIFTLIB_SINGLE_STATIC AND NOT SWIFTLIB_SINGLE_OBJECT_LIBRARY) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
80 columns, please.
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 |
@@ -1,4 +1,4 @@ | |||
add_swift_library(swiftRemoteMirror SHARED TARGET_LIBRARY DONT_EMBED_BITCODE | |||
add_swift_library(swiftRemoteMirror ${SWIFT_STDLIB_LIBRARY_BUILD_TYPES} TARGET_LIBRARY DONT_EMBED_BITCODE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean this should be hardcoded as
SHARED
, and only built whenSWIFT_BUILD_STDLIB
is 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_library
such 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_library
also checks whether the libraryIS_STDLIB
before 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.