Re: [CMake] [DKIM] Re: cmake create executable Undefined symbols for architecture x86_64:

From: CMake on behalf of Micha Hergarden Sent: 10 July 2017 21:22 To: seanwayl...@gmail.com Cc: cmake@cmake.org Subject: [DKIM] Re: [CMake] cmake create executable Undefined symbols for architecture

Re: [CMake] debugging CMAKE_PREFIX_PATH

Hi, > find_package(Qt5Core ${QT_MIN_VERSION} REQUIRED) > I build with -DCMAKE_PREFIX_PATH set, and in CMakeCache.txt, I see: > //No help, variable specified on the command line. > CMAKE_PREFIX_PATH:PATH=/usr/pkg/qt5 > //The directory containing a CMake configuration file for Qt5Core. >

Re: [CMake] cmake end user vs. developer rpath handling

From: CMake on behalf of Eric Noulard Sent: 10 October 2019 12:05 To: DIXON, MARK C. Cc: cmake@cmake.org Subject: [DKIM] Re: [CMake] cm?ake end user vs. developer rpath handling > No they can't because the maximum size is burried into the binary ELF file, >

Re: [CMake] cmake end user vs. developer rpath handling

From: Eric Noulard Sent: 10 October 2019 14:43 To: Zakrzewski, Jakub Cc: cmake@cmake.org Subject: Re: [CMake] cmake end user vs. developer rpath handling > So I was wrong, thank you for your honest question Jakub. > I learned something usefull thanks

Re: [CMake] cmake end user vs. developer rpath handling

From: CMake on behalf of DIXON, MARK C. Sent: 08 October 2019 17:25 To: cmake@cmake.org Subject: [CMake] cmake end user vs. developer rpath handling >Sometimes, this does the trick. When it does, I'm very happy: > > cmake -D