Re: [CMake] CMAKE_SIZEOF_VOID_P question
> Next question is then why doesn't GNUInstallDirs set > CMAKE_INSTALL_LIBDIR as I expect on Ubuntu for the example I gave? > > I am expecting to see either lib64/lib (for 64/32 bit) or a triplet for > (32-bit). Now it's always 'lib'. Debian / Ubuntu injects this additional triplet for multiarch support [1]. As far as you are concerned, you can safely ignore this detail. [1] https://wiki.debian.org/Multiarch Ghis -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Platform-independent config package
Dear all, I am currently hit by an issue with the CMake detection of a header-only library [1]. The library is built on a 64-bit machine and packaged for all other architectures supported by Debian. However, CMake detection fails on 32-bit platforms with the following error: ``` Any attempt to call `find_package(glm REQUIRED)` produces the following error: ``` Could not find a configuration file for package "glm" that is compatible with requested version "". The following configuration files were considered but not accepted: /usr/lib/cmake/glm/glmConfig.cmake, version: 0.9.8 (64bit) ``` How can this be effectively solved? Can the bit-ness detection be dropped somehow? It should not be needed for a header-only target. Cheers, Ghis [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850277 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Comments and improvement on find modules
Dear CMake users,
I have recently written a set of find modules [1][2][3] for dependencies
I use for the project I am currently working on. I made sure to write
them in a style that is close to what is currently maintained in CMake,
with the goal to submit them for inclusion upstream and benefit the
whole community.
I wanted to ask you guys for comments regarding their content. Some
things may be superfluous, others may be missing or improved. Any piece
of feedback is warmly welcome.
I was also wondering whether there is some sort of best practice with
regards to the handling of user-defined prefixes for custom locations of
dependencies. I saw some modules using ${Pkg}_ROOT, others using
${Pkg}_DIR, some using a cached variable...Could you guys point me to
what is considered good examples here.
[1]
https://github.com/ghisvail/IRTK/blob/enh/cmake-find-modules/CMake/FindFLANN.cmake
[2]
https://github.com/ghisvail/IRTK/blob/enh/cmake-find-modules/CMake/FindLibLBFGS.cmake
[3]
https://github.com/ghisvail/IRTK/blob/enh/cmake-find-modules/CMake/FindNiftiCLib.cmake
Many thanks,
Ghislain
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
