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
AppVeyor CI - Windows builds #192
Comments
|
Some problems I found so far:
|
|
hardcoding the path to libvlc allows vlc-based project to build, so vlc nuget is a valid project. |
|
Managed to build libglest (vs2019), but I had to copy some headers out of SDL2 directory in vcpkg folder and I had to manually specify lib directories. |
|
Linked everything and glest_game appears to build, but the linker leaves me with 3300 + errors (mostly "unresolved external symbol"). |
|
Now using libglew from nuget, because version from vcpkg is too new. Build gets so far then fails catastrophically at linking |
|
I made a second attempt at building on windows with vcpkg, with no luck I have no idea what I'm doing at this point. Some forum posts online would suggest additional libs need linking, but who knows what the right libs to link are or how you find out which need linking. There's no online help for these specific link errors, afaik. Anyone else wants to give it a try with what I've done can look at this branch https://github.com/MegaGlest/megaglest-source/tree/vcpkg_build |
|
It seems that there are many reasons for these so-called LNK2019 warnings. Whoever works on this next might get some hints at https://stackoverflow.com/questions/19886397/how-to-solve-the-error-lnk2019-unresolved-external-symbol-function This was one of my favorite answers ;)
|
|
I've pushed some more changes to https://github.com/MegaGlest/megaglest-source/tree/vcpkg_build Megaglest now builds, but fails to run. All that happens is the game starts, the loading spinner flickers, and I get this in console: The game then ends. No other info is provided. This maybe because I'm building with |
|
I ran it in verbose to get some more info, but nothing obviously suspicious: |
|
Steps to reproduce what I've done so far:
These steps will successfully build megaglest, but it will not run properly and there will be no errors. I tried copying and running it in the same directory as my standard megaglest installation and running it with |
|
I have been re-attempting this, with a lot more success (mainly thanks to @andy5995 ). This uses vcpkg+cmake+msbuild. I tested it using visual studio c++ tools + vscode. It's quite nice because you don't have to install the visual studio ide. You can compile it by running vcpkg+cmake+msbuild commands. I had some problems with the function My next plan is to make a new branch, with the cmake corrected properly, rather than just hacked. Hopefully can create debug+release build options, rather than just debug. |
Creating a ticket here to keep track of building on appveyor.
Problems with package manager
Libs which are not available on vcpkg:
So the package I think that is the biggest problem is libircclient
The text was updated successfully, but these errors were encountered: