Openapoc: Are dependencies required to be built from sources?

Created on 8 May 2020  路  2Comments  路  Source: OpenApoc/OpenApoc

From 8 dependency libraries found in dependencies 6 are available through vcpkg (except libsmacker and tinyformat).

Does OpenApoc use some custom/specific versions of those libraries and thus cannot import them from vcpkg?

If not I'd like to switch to vcpkg to reduce compilation times.

Most helpful comment

Yeah, I realize vcpkg is mostly used on Windows only.

It's just the development on Windows could benefit from importing packages from vcpkg instead of building where possible. And IMO this stands for other platforms too -- resorting to building a package from sources only when the native package is not available or is unsuitable.

All 2 comments

Some use custom patched versions (like libsmacker and physfs), some require pinned versions (while I think we can now use the latest version of glm, there's been some api changes that we've had to workaround)

Also the dependencies/ directory was created before vcpkg was a thing, and on some platforms that already have system package managers (e.g. most Linux distros) vcpkg isn't really a good solution globally.

Yeah, I realize vcpkg is mostly used on Windows only.

It's just the development on Windows could benefit from importing packages from vcpkg instead of building where possible. And IMO this stands for other platforms too -- resorting to building a package from sources only when the native package is not available or is unsuitable.

Was this page helpful?
0 / 5 - 0 ratings