I finally have C::B windows building on Github actions, but it takes ages (3hrs) in total from start to generating the C::B exe.Good!
It does not include generating the installer as this step is failing. If anyone can help reduce the time I would gratefully appreciate the help, but be aware that building locally and building on Github are not the same as the Github environment is a 2xCPU virtual Windows 2019 machine.So, you mean 3 hours is the time running in your local PC? not the virtual CPU in the Github environment?
But, 3 hrs is too long. :(3hrs on Github.com. You can look at the repo and see it in the actions results.
So, you mean 3 hours is the time running in your local PC? not the virtual CPU in the Github environment?
2022-05-19 (https://github.com/msys2/MINGW-packages/commits/master/mingw-w64-wxWidgets3.1) | mingw-w64-wxWidgets3.1 (https://packages.msys2.org/base/mingw-w64-wxWidgets3.1) | 3.1.5-6 | → | 3.1.6-1 | Ready for upload but waiting for dependencies |
Thanks, do you know if C::B will work by "just" linking to it? Aka not require you to build wx 3.1.6 from source if you are using it and MSYS2?If you look at Tim's pull request, you will see that Direct2D is enabled for building C::B, so I guess the answer is Yes. :)
The current state as far as I can see is that it has been waiting for 10 days now, so based on what I have seen in the past it is stuck and it will not go anywhere without some help. The MSYS2 pending updates show it as:I don't know, maybe some MSYS2's developer can help to solve this issue.
2022-05-19 (https://github.com/msys2/MINGW-packages/commits/master/mingw-w64-wxWidgets3.1) mingw-w64-wxWidgets3.1 (https://packages.msys2.org/base/mingw-w64-wxWidgets3.1) 3.1.5-6 → 3.1.6-1 Ready for upload but waiting for dependencies
If you look at Tim's pull request, you will see that Direct2D is enabled for building C::B, so I guess the answer is Yes. :)
Well, I saw yesterday, the package information, it shows: Ready for upload.
And now, it shows: Ready for upload but waiting for dependencies.