Skip to content

Conversation

@drodriguez
Copy link
Contributor

The same that some setups needs the CMAKE_EXE_LINKER_FLAGS propagated for the test to compile plugins in the same configuration as the compiler was using, the CMAKE_SHARED_LINKER_FLAGS needs to be propagated if one wants to match the configuration used by CMake to create libraries during the tests.

Add a new config value derived from CMAKE_EXE_LINKER_FLAGS, turn that value into a substitution for the Macros tests, and use the substibution in one test that creates a shared object. This allows the shared object to be linked in the same way that it has been configured in CMake.

The same that some setups needs the `CMAKE_EXE_LINKER_FLAGS` propagated
for the test to compile plugins in the same configuration as the
compiler was using, the `CMAKE_SHARED_LINKER_FLAGS` needs to be
propagated if one wants to match the configuration used by CMake to
create libraries during the tests.

Add a new `config` value derived from `CMAKE_EXE_LINKER_FLAGS`, turn
that value into a substitution for the `Macros` tests, and use the
substibution in one test that creates a shared object. This allows the
shared object to be linked in the same way that it has been configured
in CMake.
@drodriguez drodriguez requested a review from rintaro November 20, 2025 18:14
@drodriguez
Copy link
Contributor Author

@swift-ci please smoke test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant