-
Notifications
You must be signed in to change notification settings - Fork 473
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
Begin converting to GitHub Actions #381
Conversation
This reverts commit be2c2cb.
@@ -35,7 +35,8 @@ option(BUILD_FILTERS "Build filter applications." ON) | |||
option(BUILD_GENERATORS "Build code generation applications." ON) | |||
|
|||
if(WIN32) | |||
set(SHELL PowerShell -Command) | |||
# Use bash (usually from Git for Windows) for piping results | |||
set(SHELL bash -c) |
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.
Do we know of any Windows users that can comment on this?
I know that I have bash on my Windows VM, but is that true for those who treat it as a daily driver and use git?
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.
Looks good!
Begin converting to GitHub Actions
This begins moving us over to GitHub Actions for CI. We're able to remove a few of the Travis CI tests that are now run in GitHub Actions.
GitHub Actions should make it easier to test pull requests that work with compiler flags (#372, #360, #326) since the compiler installs seem to be more "standard" compared to Travis CI, which does more custom management of the compiler installs, which can result in standard "extras" missing. Also, Github Actions seems to be faster than Travis CI or Appveyor.
Not all tests are ported, this will be addressed in a later PR. The following doesn't work: