https://docs.conan.io/2/integrations.html
Conan is used in addition to Cmake etc. Those interact. So unless I know Cmake and Conan, how they build files etc, very well, I move on. I am not a coder, I don’t use build systems or integrations daily.
CI: Introduction to Continuous Integration (CI) — Bincrafters Documentation 0.1.0 documentation
If you want to learn tho, this is your chance. You have a goal. Make it work. You “only” need to figure out how both systems work and what the intention was. Could take a day, could take weeks.
If it is an easy problem, like a missing dependency, be it a command or library, I hunt it down. Just have to figure out packagename and in the case of a command, which library or set of tools provide that command.
Story time:
I come across these things because I compile programs often. All I really need is to know what commands to run. Those almost never work. For bigger builds. Take Mesa for example. I go to Installing MESA — MESA main documentation Tried downloading Mesa SDK. Link doesn’t work. Couldn’t find mirrors or alternative sites for the file. I don’t know fortran or whatever, not trying to get another IDE to make it work. I start looking at other guides. So I try the Mesa 24.0.5 source tarball. That one complained about llvm.wrap, couldn’t figure it out. Compiled LLVM just to try and find llvm-config. Added it to Path. Found llvm-config in many places, added to the path. Still doesn’t work. That was an hour or so wasted. Find this: How to build and use mesa from source · GitHub
It is for Ubuntu. Doesn’t matter. Did I check for dependencies? Nope. Did I install any of them? Nope. I just tried to run the first ‘meson’ command. I know I have ninja/meson. I like that build system, it is simple (for me to use), it is fast, I don’t have to bother with -j8 or any such flags, it uses all my cores by default. Love it. I don’t remember if it complained about a dependency, I don’t think so. You would think I compile for a living because I have most of the stuff installed.
I only built the 64-bit part. “Config with AMD drivers only in release mode, including codecs” Spits out Mesa in my home-folder at the end, I used a prefix. Didn’t want it messing with my systems Mesa.
If you want to install to a prefixed folder, different folder than default which is often /usr or /usr/local, use it during the build process. So the first command should include it. for Meson/Ninja = meson --prefix=“foldername, absolute”. For make, ./configure --prefix=“foldername, absolute”. I don’t think it matters where you put --prefix, first, last. But usually prefix is near the beginning. If for nothing else, for ease of reading and figuring out where all the files go.
Tested a game from Steam, it worked. Goverlay/Mangohud reported Mesa 24.1.0-devel git (In Goverlay-> Metrics->Driver version in the GPU section).
I used the mesarun.sh script on the page.