-
Notifications
You must be signed in to change notification settings - Fork 79
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
base: main
Are you sure you want to change the base?
Conversation
} | ||
|
||
extension Process { | ||
func run() async throws { |
There was a problem hiding this comment.
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()
:)
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? |
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 |
Can you add that information as part of the command's help info or in comments? |
822c28a
to
83f5a82
Compare
83f5a82
to
5ded24f
Compare
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 |
@swift-ci test |
Should we query the package model from |
@swift-ci test macOS |
@neonichu I'm not sure if the context API gives us a way to determine what platforms each dependency is used on |
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. |
This is very very WIP, but it might be worth building out into a script we can use to smoke test the CMake build