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

Add a command plugin which validates the cmake based build #256

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

owenv
Copy link
Collaborator

@owenv owenv commented Mar 6, 2025

This is very very WIP, but it might be worth building out into a script we can use to smoke test the CMake build

}

extension Process {
func run() async throws {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Thank you for not using waitUntilExit() :)

@jakepetroules
Copy link
Collaborator

Other than cloning the repos, is there any other setup needed to run this script? Or does modern CMake come with all the Swift support built in and ready to go these days?

@owenv
Copy link
Collaborator Author

owenv commented Mar 6, 2025

Cloning with update_checkout is basically the only prerequisite, but this script has a bunch of small bugs and issues that need to be addressed as well

@jakepetroules
Copy link
Collaborator

jakepetroules commented Mar 6, 2025

Cloning with update_checkout is basically the only prerequisite

Can you add that information as part of the command's help info or in comments?

@owenv owenv force-pushed the owenv/cmake-plugin branch from 822c28a to 83f5a82 Compare March 25, 2025 17:49
@owenv owenv force-pushed the owenv/cmake-plugin branch from 83f5a82 to 5ded24f Compare March 25, 2025 18:37
@owenv
Copy link
Collaborator Author

owenv commented Mar 25, 2025

This is good enough to serve as a smoke test of the CMake build on macOS now, I think I'll land it and improve the rest of the platform support over time

@owenv owenv marked this pull request as ready for review March 25, 2025 18:37
@owenv
Copy link
Collaborator Author

owenv commented Mar 25, 2025

@swift-ci test

@neonichu
Copy link
Collaborator

Should we query the package model from PluginContext for the package dependencies instead of hard-coding them in the plugin?

@owenv
Copy link
Collaborator Author

owenv commented Mar 26, 2025

@swift-ci test macOS

@owenv
Copy link
Collaborator Author

owenv commented Mar 26, 2025

@neonichu I'm not sure if the context API gives us a way to determine what platforms each dependency is used on

@neonichu
Copy link
Collaborator

I think it's fine to merge either way, but this seems like a prime use case for the API, so if anything is missing that could be good candidates for evolution of plugins.

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.

3 participants