libopenvizsla icon indicating copy to clipboard operation
libopenvizsla copied to clipboard

Migrate appveyor mingw environments to vcpkg

Open matwey opened this issue 6 years ago • 11 comments

mingw triplets are supported in vcpkg currently. However, not all dependencies are installable for mingw triplets yet.

matwey avatar Feb 28 '20 07:02 matwey

https://github.com/microsoft/vcpkg/issues/9751

matwey avatar Mar 01 '20 08:03 matwey

Some dependencies still cannot be installed through vcpkg.

matwey avatar Oct 22 '20 10:10 matwey

It would be great.

Currently, libusb build is failed: https://github.com/microsoft/vcpkg/issues/9751

Also, look at https://github.com/matwey/libopenvizsla/commit/8b5ba5f637dfe8c65aa5845e01348836b5ccb533 for the reference.

Upd: Also, appveyor provides out-of-date vcpkg, and recent version cannot be rebuilt with mingw.

matwey avatar Oct 22 '20 11:10 matwey

I am not sure, I was stuck at libusb.

vcpkg is used for Visual Studio build, while mingw build uses msys binary packages now. So it would be great to handle them uniformly.

If you just need prebuild libopenvizsla binaries, then it is another issue. The build artifacts can be uploaded to GitHub releases from Appveyor CI.

matwey avatar Oct 22 '20 13:10 matwey

@sfhacker can you build statically linked Windows binaries as well?

desowin avatar Oct 23 '20 08:10 desowin

How much experience do you have building projects from source on Windows?

Just built master branch from source on Windows 10 x64 with no issues at all.

Exactly like it is happening in CI now: https://ci.appveyor.com/project/matwey/libopenvizsla/branch/master

image

image

This open issue is like 8 months old!

So what is the problem with this particular issue for you? It is not about mingw, it is about vcpkg.

Can you post here the errors you get when trying to build this project from source?

Cheers.

matwey avatar Oct 23 '20 08:10 matwey