Hi George, Jakub,
> NO_DEFAULT_PATH
>
> NO_CMAKE_ENVIRONMENT_PATH
>
> NO_CMAKE_PATH
>
> NO_SYSTEM_ENVIRONMENT_PATH
>
> NO_CMAKE_SYSTEM_PATH
>
The options specified are redundant. NO_DEFAULT_PATH implies the later 4.
If you just specify NO_DEFAULT_PATH then only HINTS and user guess pa
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of George
Sent: Dienstag, 28. Oktober 2014 13:42
To: cmake@cmake.org
Subject: Re: [CMake] FIND_PATH() search custom path first
On 28 October 2014 09:34, Jakub Zakrzewski
mailto:jzakrzew...@e2e.ch>> wrote:
> I have a situatio
> I have a situation where I need to prefer a custom-build of a library over
> any system-installed versions. I understand that the paths in the HINTS
> variable will be searched before the > system ones, but the documentation
> discourages its use with hard-coded paths.
> If I do hard-code a HI
On 28 October 2014 09:34, Jakub Zakrzewski wrote:
> > I have a situation where I need to prefer a custom-build of a library
> over any system-installed versions. I understand that the paths in the
> HINTS variable will be searched before the > system ones, but the
> documentation discourages it
Hi,
I have a situation where I need to prefer a custom-build of a library over
any system-installed versions. I understand that the paths in the HINTS
variable will be searched before the system ones, but the documentation
discourages its use with hard-coded paths.
If I do hard-code a HINTed path
