FS#61952 - [glm] cmake cannot find include directory

Attached to Project: Community Packages
Opened by Tuan (nori) - Friday, 08 March 2019, 14:18 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 08 March 2019, 21:15 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
cmake cannot find glm's include directory. It returns the following error.

CMake Error at /lib64/cmake/glm/glmConfig.cmake:10 (message):
File or directory //include referenced by variable GLM_INCLUDE_DIRS does
not exist !
Call Stack (most recent call first):
/lib64/cmake/glm/glmConfig.cmake:16 (set_and_check)
CMakeLists.txt:11 (find_package)

Additional info:
I am using glm (0.9.9.3-1).
This bug is very similar to the bug reported and solved here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827799

Steps to reproduce:
Create a CMakeLists.txt file for a project and use "find_package(glm)" to find glm.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Friday, 08 March 2019, 21:15 GMT
Reason for closing:  Works for me
Comment by Eli Schwartz (eschwartz) - Friday, 08 March 2019, 21:15 GMT
There is something wrong on your system, as it is seeing /lib64/cmake/glm/glmConfig.cmake in /lib64 instead of finding it in /usr/lib64 -- therefore it is also trying to detect the directory as /include, rather than /usr/include.

I cannot duplicate this locally, and find_package(glm) works flawlessly for me. cmake is supposed to only search under /usr so I would encourage you to investigate why it is not doing so for you.

Note that the Debian bug is completely unrelated; in that case, the Debian packaging had moved files around which contained relative paths, thereby breaking the relative pathnames.

Loading...