-
Notifications
You must be signed in to change notification settings - Fork 10.5k
build: use modern target property handling #29451
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 clean test |
Build failed |
Build failed |
6cd1c96
to
04adc97
Compare
@swift-ci please clean test |
Build failed |
Build failed |
04adc97
to
4970eb3
Compare
@swift-ci please clean test |
Build failed |
@swift-ci please clean test |
Build failed |
Use specific operations for setting the compile flags, link flags, linked libraries, and library search paths. This allows us to use CMake more effectively, simplifies the logic, and will ensure that flags are not duplicated.
4970eb3
to
d8b3b62
Compare
@swift-ci please clean test |
Build failed |
@swift-ci please clean test |
This should repair the Windows build after swiftlang#29451. The quoting behaviour was incorrect and was constructing an invalid compiler invocation. Solve the issue by using `target_include_directories` instead. However, since this needs the target, hoist the flag computation to the local sites. This replicates more logic because of the custom build trying to replicate the CMake build logic in CMake.
Before the result of `_add_variant_c_compile_flags` was a string, so appending several "-isystem" was not a problem. With swiftlang#29451 the rules have changed since the list is now handled by CMake, and it deduplicates the repeated members in the list. Thanks, CMake. Should fix the Android CI builds that were failing since the merging of swiftlang#29451.
Collate -F with the framework path to avoid unwanted deduplication of options by `target_compile_options` (which is the case after swiftlang#29451) -- this way no undesired side effects are introduced should a new search path be added. Addresses rdar://problem/58934566
Collate -F with the framework path to avoid unwanted deduplication of options by `target_compile_options` (which is the case after #29451) -- this way no undesired side effects are introduced should a new search path be added. Addresses rdar://problem/58934566
Generator expressions seem not to allow the `LINKER:` prefix to be expanded correctly when used in `target_link_options`. To solve this, undo the change from swiftlang#29451 and instead use an `if` statement to add the flag when needed. Addresses rdar://problem/59117166
This should repair the Windows build after #29451. The quoting behaviour was incorrect and was constructing an invalid compiler invocation. Solve the issue by using `target_include_directories` instead. However, since this needs the target, hoist the flag computation to the local sites. This replicates more logic because of the custom build trying to replicate the CMake build logic in CMake.
There was a mixup in swiftlang#29451 and a CMake flag was dropped, this puts it back. Resolves SR-13315
Use specific operations for setting the compile flags, link flags,
linked libraries, and library search paths. This allows us to use CMake
more effectively, simplifies the logic, and will ensure that flags are
not duplicated.
Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.
Resolves SR-NNNN.