Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 3200

Programming • Meson dependencies: Homemade and missing dependencies

$
0
0
I read a lot about how to configure Meson, it's pretty neat, there are various ways to find your dependencies and just adding the dependency name solve the requirement. When it's something know and popular, like sqlite3, there is no problem.

The problem is for obscure and homemade dependencies. I crease multiple small libraries to decompose my projects. Those libraries are not going to be in pkg-config list, or in a distro package. I could have a git repo location for those libraries and handle them as a sub-project using a wrap file, but that brings another problem: Duplication.

For example, if I want to use Raylib, this dependency cannot be found. If I setup a wrap file as a sub-project, it will download and compile the entire library. If I have 4 projects, it will download 4 copies of that same library. If I push my project on gitlab, the gitlab runner is going to download Raylib and build it every push consuming a lot of runner time.

In normal circumstances, the library would have been built once and install on my system for all applications. As for the gitlab runner, either I need to install the package from the distro, or build the library once and upload the artifacts on another server, then included later by the projects using this lib.

How can I use local libraries manually installed or from distro package?

Can I create my own pkg-config files to make it find my local libs?

How can I include binary libs for the runner, does using a simple file dependency in a zip sufficient?

I imagine, following this logic, to minimize download and avoid unnecessary build time, I could download library artifacts in zips instead of code?

Statistics: Posted by larienna — 2024-10-21 06:39 — Replies 0 — Views 52



Viewing all articles
Browse latest Browse all 3200

Trending Articles