Build dependencies with vcpkg for Linux #24
Conversation
|
Quite a lot of this is very similar to the equivalent for Windows, so have you considered setting different operating systems up with |
This would require adding |
| sudo apt install -y | ||
| autoconf-archive | ||
| libegl1-mesa-dev | ||
| libgl-dev | ||
| libibus-1.0-dev | ||
| libltdl-dev | ||
| libwayland-dev | ||
| libx11-dev | ||
| libxext-dev | ||
| libxft-dev | ||
| libxkbcommon-dev | ||
| nasm |
There was a problem hiding this comment.
Are we installing these because they all have a distro-independent ABI and we expect the non-dev packages to be installed on all user machines? If so, we may want a comment saying so.
| - name: Generate files containing a download url and hash for linux | ||
| run: | | ||
| mkdir -p openmw-deps/linux | ||
| src=vcpkg-x64-linux-${{ env.file }}.7z |
There was a problem hiding this comment.
It might be sensible to include the compiler and version in the name like we do for Windows as it affects the ABI, just like it does on Windows. Thinking about it, it might have made some sense to put msvc2022 in the Windows filenames instead of just 2022, but it's not as big a deal as for Clang and GCC as 2022 won't get confused with 20 or 14, but it's not as obvious that 14 is a GCC version rather than a Clang one.
To set up generic Linux builds in CI. Use approach similar to windows.