DLib_LIBRARY NOTFOUND about badslam

[puzzlepaint]

I'm afraid I can't point to anything specific. In general, if you had to modify the DlibConfig.cmake file, it sounds to me like something may be wrong with the DLib installation, since I would normally expect that to work out-of-the-box.

On my current system, DLib_LIBRARY is set to <dlib's_installation_directory>/lib/libDLib.so. So, I guess that looking for the libDLib.so file and pointing the search path in DlibConfig.cmake to its directory may be a workaround.

Also notice that there are at least two libraries called "DLib", badslam requires this one. If the DlibConfig.cmake file you quoted was installed by the library, then it seems to be the correct one though.

[dianaleeg]

Hey there @puzzlepaint , i appreciate the response! Hmm, im wondering if it has to do with the way I am using cmake? I created a new directory 'build' inside of DLib, then i navigate to the folder 'build' and then run cmake .. .

($ mkdir build, $ cd build, $ cmake .. )

I did notice that I dont have a shared object file -- is this supposed to be a result of cmake? I don't see it in the repository either.

(I can verify that that is the DLib that I installed!)

[dianaleeg]

AH-HA, i was missing $ make

Thank you very kindly for your response. All is working!

[puzzlepaint]

Usually, one would also run make install after make, possibly with sudo if necessary. This copies all the relevant output files produced by make to the installation location (which is likely under the /usr/local prefix by default), where they are supposed to be found later by CMake for badslam (if CMake is told to use this installation rather than the path you used before).

Perhaps omitting the installation causes the include files directory not being set properly as in #37.

[dianaleeg]

AH yes! That did solve my issue, thank you very much for your help.