-
Notifications
You must be signed in to change notification settings - Fork 73
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
CI / continuous testing would be nice #65
Comments
Yes that would be done in a secound step. |
Which kind of approach would you prefer for the github action workflow: A more "native" and "splitted" approach as for example here: Or a cmake based "all in one" definition as for example here: https://github.com/cristianadam/HelloWorld/tree/master/.github/workflows |
If it's a comparable amount of work and functionality, I think I prefer the "split" approach - a bit easier to digest and work on, perhaps ? |
I just asked for personal preference. I would tend to "split" approach as well. So decision made: 1 workflow definition per architecture. |
from PR #64 , the ability to test compilation on MSVC + borland + mingw automatically would be nice.
ctest
tests that don't require a hardware interface (currentlyctest -I 3 ...
)The text was updated successfully, but these errors were encountered: