Camera plugin are linking Lima's indirect dependencies

The link phase shows that all dependencies of Lima and Processlib are linked to the (simulator) plugin:

g++ ... -o liblimasimulator.so.1.9.8 CMakeFiles/simulator.dir/src/SimulatorFrameBuilder.cpp.o CMakeFiles/simulator.dir/src/SimulatorFrameLoader.cpp.o CMakeFiles/simulator.dir/src/SimulatorFramePrefetcher.cpp.o CMakeFiles/simulator.dir/src/SimulatorCamera.cpp.o CMakeFiles/simulator.dir/src/SimulatorInterface.cpp.o CMakeFiles/simulator.dir/src/SimulatorSyncCtrlObj.cpp.o CMakeFiles/simulator.dir/src/SimulatorDetInfoCtrlObj.cpp.o CMakeFiles/simulator.dir/src/SimulatorShutterCtrlObj.cpp.o CMakeFiles/simulator.dir/src/SimulatorBinCtrlObj.cpp.o CMakeFiles/simulator.dir/src/SimulatorRoiCtrlObj.cpp.o  /home/debionne/miniconda3/envs/foo/lib/liblimacore.so.1.9.19  /home/debionne/miniconda3/envs/foo/lib/libprocesslib.so.1.9.0  -lpthread  /home/debionne/miniconda3/envs/foo/lib/libgsl.so  /home/debionne/miniconda3/envs/foo/lib/libgslcblas.so  -lz  -llz4  -lcbf  -lcrypto  -lhdf5_cpp  -lhdf5  -lhdf5_hl_cpp  -lhdf5_hl  -lhdf5_cpp  -lhdf5  -lhdf5_hl_cpp  -lhdf5_hl  -ltiff  -lconfig++  -lrt  -lnuma

This behavior is described in the CMake LINK_LIBRARIES doc:

The value of this property is used by the generators to construct the link rule for the target. The direct link dependencies are linked first, followed by indirect dependencies from the transitive closure of the direct dependencies' INTERFACE_LINK_LIBRARIES properties. See policy CMP0022.

Making all dependencies of Lima PRIVATE so that they are not transitively linked to downstream projects should fix it.