Skip to content
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

Configure CMake rules to install content into toolchain #531

Closed
wants to merge 4 commits into from

Conversation

stmontgomery
Copy link
Contributor

This includes several changes to the CMake rules to support installing built content into a toolchain.

Motivation:

This is necessary to support including swift-testing in Swift 6 toolchains.

Checklist:

  • Code and documentation should follow the style of the Style Guide.
  • If public symbols are renamed or modified, DocC references should be updated.

@stmontgomery stmontgomery added enhancement New feature or request tools integration Integration of swift-testing into tools/IDEs build Affects the project's build configuration or process labels Jul 10, 2024
@stmontgomery stmontgomery self-assigned this Jul 10, 2024
@stmontgomery
Copy link
Contributor Author

@swift-ci please test

@@ -97,7 +97,8 @@ target_link_libraries(Testing PRIVATE
add_dependencies(Testing
TestingMacros)
target_compile_options(Testing PRIVATE
-enable-library-evolution)
-enable-library-evolution
-emit-module-interface -emit-module-interface-path $<TARGET_PROPERTY:Testing,Swift_MODULE_DIRECTORY>/Testing.swiftinterface)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible for us to emit our private interface too, so that developers could use @_spi symbols?

@grynspan
Copy link
Contributor

@compnerd @jeffdav please take a look.

@stmontgomery
Copy link
Contributor Author

Note this PR is still a draft, I have TODO comments I know I still need to resolve

# This is not the plugin's actual, final install location -- it's only
# relative to this external project's install dir. The final location is
# determined by the "outer" project.
install(TARGETS TestingMacros DESTINATION "")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you leave off the DESTINATION ""?

@stmontgomery stmontgomery force-pushed the toolchain branch 2 times, most recently from c1da06f to 2e882c6 Compare July 16, 2024 18:23
@grynspan
Copy link
Contributor

Closing as this PR has been superseded by #581.

@grynspan grynspan closed this Aug 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Affects the project's build configuration or process enhancement New feature or request tools integration Integration of swift-testing into tools/IDEs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants