Adding path to ldconfig?

Synaptic

Hello,

I’ve had to prebuild some libraries from source (which I’m perfectly fine with) but my small problem is that linkers are unable to find the built libraries in /usr/local/lib as Solus doesn’t use the local hierarchy.

Normally there are two options I believe, one is to push your custom .conf in the /etc/ld.so.conf.d directory which also I believe is missing in Solus.

what are my options here?
would using ldconfig -n append the new path to search for dynamic libs there? Or adding LD_LIBRARY_PATH to bashrc? (Can you add more than one? I was always confused with this path flag tbh) those libraries utilise pkgconfig as well which I probably forgot to add PKG_CONFIG_PATH…

Thank you!

stalebrim

Synaptic Do you build the libraries with solbuild?

Synaptic

stalebrim
No I have never heard of solbuild. What is that tool for?
just FYI I’m not building a package, I’m building a 3rd party library with cmake to use for myself that defaults to installation in /usr/local and LD linker can’t find it in that hierarchy because Solus doesn’t use it… As mentioned on my first post

stalebrim

Synaptic Solbuild is the system for building Solus packages. I think that it would make sense to wrap the lib you need as a package, because the build system is (as far as I know*) able to put things where they work under Solus.

The Help Center has a bunch of helpful articles on building a package under Solus and using solbuild. https://getsol.us/articles/packaging/

(* asked @Staudey, he said "Depends on how the Makefile is structured really. Hardcoded things will need to be overridden or patched out still. For sensible Makefiles it should put everything in the right places.")

stalebrim

Why do they have to be in /usr/local?

Synaptic

stalebrim

Its just easier to do it that way as I’m not quite too sure what’s best way to edit makefiles or cmake files on where they need to go and where they should actually go?

EDIT:
All good now, I managed to get this sorted out.