-
Notifications
You must be signed in to change notification settings - Fork 14
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
Enable actual build tests in Windows/Appveyor CI #83
Comments
I took a glance at the Windows builds linked from https://github.com/emaculation/macemu previously and was confused about the state of the build jobs because they say 'MSYS' above the links but the build jobs are using Cygwin, not MSYS. I guess that this build setup with Cygwin is something that would have worked with the older codebase, and once upon a time this was the main way of building, but it doesn't work at the moment. (See below.) If you look at Appveyor's list of installed software in build VMs, in the "MinGW, MSYS, Cygwin" category
So MSYS would be either the first one or the last one. Background:
This is a typical kind of problem you get when you build code intended for MinGW for the regular Cygwin POSIX environment instead: The APIs from Windows headers run into the APIs from the POSIX-style headers. On Windows, normally the only There was an option in the Cygwin |
I already have an Appveyor build job for macemu using MSYS2 that I'm using to build branches off of kanjitalk755's repo. I don't have an |
Why, in |
Er, also https://github.com/emaculation/macemu says "32-bit" but your |
Wait, is the Windows code in the master branch here actually in a buildable state at all?
|
I can't speak to whether this branch is buildable, for how long it hasn't been buildable. I put this project on GitHub (forking from the original and doing my best to merge in the latest from actively developed forks like @kanjitalk755 has) in an attempt to bring its development into the GitHub age -- with all the continuous integration and pull request reviewing that we expect in 2020. Not having access to a windows machine (aside from Appveyor's remote option), I'm really not sure how to push the config forward and I will gladly accept any working build scripts that you have on this platform! What you're seeing here is my own trial and error that ultimately resulted in me reaching the limits of my expertise there. |
One way to get a 'Windows machine': Microsoft provides VM images with 90-day unactivated trial copies of the Windows for IE/Edge browser testing, but these that will run software other than the browser provided that it works without installing additional OS components that require activation. The license permits non-commercial testing use and does not specify browser use particularly. If you don't already have a virtualization software installed that you prefer I recommend VirtualBox, but if you're on a Linux distro that doesn't package VirtualBox and does package a KVM frontend like virt-manager, you may want to figure out how to use that instead. https://github.com/lentinj/ie-vm (These are referred to as 'modern.ie' VMs because before the era of Edge they used to be distributed from Microsoft's modern.ie site) |
One of the items on my to-do list is to set up a Vagrant config for Windows to simplify the process of testing in it if you don't normally deal with it. |
The Appveyor folks have a good solution for this which I had tried earlier: https://www.appveyor.com/docs/how-to/rdp-to-build-worker/ I'm just not an expert in installing any of the dependencies or MinGW builds (I come from a Linux background) so that's where I got stuck with remote desktop |
I think this can be closed, as we are now testing a build in Appveyor |
Appveyor is running a null test right now as proof of concept. Replace with a build test
Build matrix
How To Build
These builds need to be installed SDL2 framework/library.
MinGW32/MSYS
also:
https://www.emaculation.com/doku.php/compiling_sheepshaver_basilisk
The text was updated successfully, but these errors were encountered: