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

Fix Windows CI #1

Open
ianfixes opened this issue Jul 17, 2019 · 4 comments
Open

Fix Windows CI #1

ianfixes opened this issue Jul 17, 2019 · 4 comments
Labels
CI Continuous Integration help wanted Extra attention is needed Windows Affects Windows Build

Comments

@ianfixes
Copy link
Member

Set up Windows CI using Appveyor

@pruten to provide information on the build process

@ianfixes ianfixes added help wanted Extra attention is needed CI Continuous Integration Windows Affects Windows Build labels Jul 17, 2019
@ianfixes
Copy link
Member Author

ianfixes commented Sep 9, 2019

This is party done -- the CI runs -- but we are blocked until I can find a way to install SDL2 on the appveyor machines and have that installation be recognized by the build scripts.

@ianfixes ianfixes changed the title Set up Windows CI Fix Windows CI Sep 9, 2019
@tsal
Copy link

tsal commented May 5, 2020

As an interested party (not so much in Windows build, but in the repo) - how far of a stretch would it be to port the build to use visual studio 2019 + cmake? vcpkg is really good at installing frameworks and libraries pre-wired in appveyor to be available to the builds.

@ianfixes
Copy link
Member Author

Sorry for my pandemic-related distraction on this, cmake is 100% what I'm interested in at the moment, not just for this but for the macemu projects as well.

My cmake skills are rusty, especially when it comes to files that are generated by an external program prior to build, and then used as sources. But I will welcome (& assist as I can) any cmake-based build progress.

@rakslice
Copy link

I'd be much obliged if you can take 5 minutes to look at #1 and see if that windows build is misconfigured in some obvious way

I mean, why is it configured to do what it's doing now? I don't know much about cygwin 64, or shoebill, but presumably if it's missing a header you make sure the package it would be in is in the list of packages you're installing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration help wanted Extra attention is needed Windows Affects Windows Build
Projects
None yet
Development

No branches or pull requests

3 participants