Hi!
I’m preparing a PR for osm-gps-map v1.2, and I need to test it in darktable.
How do I tell darktable to compile with my custom osm-gps-map code?
Hi!
I’m preparing a PR for osm-gps-map v1.2, and I need to test it in darktable.
How do I tell darktable to compile with my custom osm-gps-map code?
You usually don’t tell darktable to do it, you build the package on your system and make sure it is on your path. Cmake should pick it up.
I find the flatpak manifest an easy way to test these kinds of changes without changing your system libs, if you’re willing to invest a little time into learning about flatpak.
I have
/usr/local/lib/libosmgpsmap-1.2.a
/usr/local/lib/libosmgpsmap-1.2.la
/usr/local/lib/libosmgpsmap-1.2.so
/usr/local/lib/libosmgpsmap-1.2.so.1
/usr/local/lib/libosmgpsmap-1.2.so.1.1.1
but even with /usr/local/lib/
in my PATH it doesn’t find it.
Does darktable looks for every version of libosmgpsmap?
Most things uses the first compatible version they find on the path.
prefix path:
cmake -DCMAKE_INSTALL_PREFIX=/opt/darktable -DCMAKE_PREFIX_PATH=/usr/local/ …/.
and if I use build.sh ?
I don’t use this script.
I use the command above followed by :
sudo make install -j8
At least on my system, a lot of such “different” .so versions are symbolic links to the most precise version of the library (in your case, /usr/local/lib/libosmgpsmap-1.2.so.1.1.1). Which basically means that it doesn’t matter which name the program is looking for.
Also, PATH defines where the system looks for executables, not libraries (for that, I think you’d need LD_LIBRARY_PATH)