-
Notifications
You must be signed in to change notification settings - Fork 56
actions: Add a configure-cmake-project action #999
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
base: main
Are you sure you want to change the base?
Conversation
@compnerd I noticed we have a few differences in flags:
Should we unify these? And if so, which way should we go? |
Yes, we should! For the Android side, actually the GHA is the ideal form. For the Windows side, the build.ps1 side is better IMO. |
os: | ||
description: Operating system to build for (e.g., "Windows", "Android"). | ||
required: true | ||
arch: |
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.
Can we name these host-os
and host-arch
?
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.
I do not think they should, as they can be either build
, host
or target
depending on the job.
ca52164
to
90104d5
Compare
This brings in a modified version of `build.ps1` from the swift repository as a custom action. This reduces the differences in the build setup between the swift repository and this repository, making it easier to keep both builds in sync.
90104d5
to
3a1c55b
Compare
This brings in a modified version of
Build-CMakeProject
inbuild.ps1
from the swift repository as a custom action. This reduces the differences in the build setup between the swift repository and this repository, making it easier to keep both builds in sync.The new reusable action only configures the CMake project in order to keep the build and install steps as separate steps in the GitHub Actions UI.