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 AppVeyor CI #25

Merged
merged 1 commit into from
Sep 12, 2018
Merged

Add AppVeyor CI #25

merged 1 commit into from
Sep 12, 2018

Conversation

Croydon
Copy link
Contributor

@Croydon Croydon commented Sep 11, 2018

Testing for different VS version is hard/not possible for @lexxmark locally. So let's change this by adding a continuous integration platform and automate this 😄

This generates the following build matrix:

[VS2015, VS2017] x [x64, Win32] x [Release, Debug] + [VS2013 Release win32]

You can see the results here:

https://ci.appveyor.com/project/Croydon/winflexbison/build/1.0.6

AppVeyor is completely free for open source projects. You need to activate AppVeyor before merging this. To do this go to https://ci.appveyor.com login with out GitHub account and enable the winflexbison project.

Happy testing! 😄

@GitMensch
Copy link
Collaborator

Thank you, this is really useful, but would be even more useful if we'd integrate the bison/flex testsuites, tracked in #17 and verify that the resulting binaries actually work...
But I assume you could find some sample tests (maybe a little bit more complex bison/flex sources), translate them with the resulting binaries and run the resulting C files through the same C compiler.
@Croydon Can you investigate this?

Additional and likely easier: it would be useful to create artifacts to enable testing from master without the need to actually compile it. @Croydon Would you be so kind?

@Croydon
Copy link
Contributor Author

Croydon commented Sep 11, 2018

I'm sorry, but creating test cases is way out of my scope why I'm contributing here in the first place (I want to package winflexbison, so I can progress in packaging doxygen, so I can package....). If I'm getting lost in every single step on the way then I will totally loose focus 😄
Also I know simply too less about how to use flex and bison.

I would recommend to merge this now to get some form of testing going. Then work on creating tests, if you have tests add them to AppVeyor.

@GitMensch
Copy link
Collaborator

GitMensch commented Sep 11, 2018 via email

@lexxmark lexxmark merged commit a760c46 into lexxmark:master Sep 12, 2018
@Croydon Croydon deleted the croydon/appveyor branch September 13, 2018 00:02
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