-
Notifications
You must be signed in to change notification settings - Fork 219
libllbuild: make the library static and internalise it #852
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
Conversation
|
@swift-ci please test |
|
@swift-ci please smoke test |
|
@swift-ci please smoke test |
|
CC: @etcwilde @DougGregor |
This has been made static with swiftlang/swift-llbuild#852. Adjust the packaging rules accordingly.
|
@swift-ci please smoke test |
|
@swift-ci please smoke test |
1 similar comment
|
@swift-ci please smoke test |
|
@swift-ci please smoke test |
|
Ping here as merging #859 alone is breaking the Windows build |
|
@swift-ci please smoke test |
|
@swift-ci test Windows |
|
@swift-ci please test |
|
@swift-ci please test Windows |
|
@swift-ci please smoke test |
1 similar comment
|
@swift-ci please smoke test |
|
@swift-ci please smoke test |
|
@swift-ci please smoke test |
|
@swift-ci please smoke test |
|
@swift-ci please smoke test |
Rather than emitting `libllbuild` as a dynamic library, expose it as a static library. This is used by a single user (`llbuildSwift`), and thus allows for simplification of the distribution. We no longer export libllbuild as the clients are using llbuildSwift. Because the module is not imported as `@_implementationOnly`, we need to expose the include path for `libllbuild` to clients of `llbuildSwift`.
|
@swift-ci please smoke test |
The libllbuild library has been converted into a static product and interalised into libllbuildSwift. This avoids the distribution issues here. Remove the library from the install set.
Utilities: adjust install rules for swiftlang/swift-llbuild#852
This has been made static with swiftlang/swift-llbuild#852. Adjust the packaging rules accordingly.
… statically linked Now that libllbuildSwift is statically linked against libllbuild with swiftlang#852, remove the runpath and don't install it. Also, the Android build started failing, so set the appropriate flag for it to work again.
… statically linked Now that libllbuildSwift is statically linked against libllbuild with #852, remove the runpath and don't install it. Also, the Android build started failing, so set the appropriate flag for it to work again.
Convert libllbuild into static and avoid exporting the library for use in other projects. The expected clients are only reliant on llbuildSwift. This overall saves some space (~20K). Additionally, it will simplify the redistribution in the toolchain by reducing the number of shared libraries while saving space.