Use Github Actions to Build

[naveen521kk]

I see @stuaxo setting up a script to update dependencies. Also, I prefer setting up a CI(May be Github Actions) to build and release when anything is updated. This would help us maintain the version of Cairo to latest and can be automated.

I tried https://github.com/naveen521kk/cairo-windows/runs/1037141588. Maybe if @preshing help me we can complete this easily.

[preshing]

Out of curiosity, why do you and @stuaxo want such bleeding-edge cairo-windows builds? Cairo doesn't change that much from one version to the next. That why I've been happy just running it manually once in a while. Maybe your needs are different from mine.

Nonetheless, if you can get it working with a CI in your fork, that would be cool. Though I expect it will continue to break occasionally as the build tools & dependencies change.

According to the log you linked, devenv.com "projects\vstudio\vstudio.sln" -upgrade fails because vstudio.sln (in the libpng archive, downloaded from https://download.sourceforge.net/libpng/libpng-1.6.37.tar.gz) doesn't need to be upgraded. That's a strange error message because vstudio.sln is a VS2010 file (!) which normally can't be used by VS2017 unless upgraded.

Even stranger is that I don't get that error message when I perform the build steps on my local machine.

One difference I see is that in the GitHub Actions log, the Visual Studio version info is:

Microsoft Visual Studio 2017 Version 15.0.28307.1234.

whereas on my local machine, it's:

Microsoft Visual Studio 2017 Version 15.0.28307.1146.

I don't know if that's enough to explain the difference. Maybe there are other differences that I've missed too.

[preshing]

I upgraded my VS2017. It's now the same version as in the GitHub Actions log:

Microsoft Visual Studio 2017 Version 15.0.28307.1234.

Still, I can't reproduce the error message locally. 🤔

[naveen521kk]

Out of curiosity, why do you and @stuaxo want such bleeding-edge cairo-windows builds?

Yes we wanted to depend on the DLL provided see pygobject/pycairo#191 and that's why we wanted

• Cairo up to date.
• Enable tee surface

[naveen521kk]

@preshing I suspect this is because maybe I had to manually add the path, and if I set it to inherit it shows a cygwin.dll error in mysys terminal. So I manually added the path. See https://github.com/naveen521kk/cairo-windows/blob/90803ab0858832273e2b28648ca2c12ef0b59204/.github/workflows/build.yml#L26 . Maybe that's the issue. But really I don't know. Also, maybe let's configure it to work with VS2019 also.

[stuaxo]

@preshing it's for pycairo which is language bindings for cairo + tends to track the latest cairo version.

@naveen521kk
I think what might be tricky here adding the 64 bit build target using just the commandline.

The README shows how to add the x64 target via the IDE, can this be done on the commandline ?

[naveen521kk]

The README shows how to add the x64 target via the IDE, can this be done on the commandline

I don't know about that.

[naveen521kk]

I just on googleing found that there is file located at C:\Program Files (x86)\Microsoft Visual Studio\2017\community\Common7\tools\VsDevCmd.bat which will add the path variables. Maybe I will try that instead of manually adding and check for it.

[stuaxo]

Have a go if you get a chance. I will get back to this in the next few days now.

The main issue seems to be that the solutions(s?) need the x64 target adding to them, which seems to need the IDE afaict.

Once it's added you can choose it and build x64 whenever.

Maybe we should add it, the upstream that to libpng and whichever of the others (ie zlib) that need if, then we can build them here without needing the manual step.

It's def something I want to try depending on how much free time I can get.

I think this is the last of the yaks to shave :)

[naveen521kk]

I don't think I will be having time to look into this. Sorry.

[stuaxo]

I don't think I will be having time to look into this. Sorry.

No problem, you've done loads of bits already - if I get some try and do this, but could be a while.

[naveen521kk]

Used some effort to make this and I could actually pretty much run in Appveyor today. All deps build it well but sadly cairo failed. If anyone could help me we can set it up to build it. @preshing could you help me here? After that, a PR would automatically build it and publish.

[stuaxo]

I need to catch up and remember what didn't work on this again.

In appveyor something weird is getting passed to link.exe
https://ci.appveyor.com/project/naveen521kk/cairo-windows/builds/35621124#L681

[naveen521kk]

Possibly because Makefile.win32 is not edited properly? There should be some copypasta mistake there I 🤔. But need check it. Because I change it to a powershell script.

[naveen521kk]

Also, is it possible to use meson here?

[stuaxo]

Nice... what's the best way to grab your stuff so I can try running it locally, is there a .appveyor directory somewhere ?

Meson, would be fantastic - it looks like it may well be possible
https://gist.github.com/demotomohiro/25f4d86c5b3a90baa8c1a77806c40bd9