On 09/14/2015 03:05 AM, CHEVRIER, Marc wrote:
> Any news on this subject?
Chuck has had a fix in 'next' for a few days:
find_*: Fix search order when the environment duplicates some HINTS
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ec8e5fb3
but the topic is still missing a test case.
Any news on this subject?
I think it is a critical bug because behaviour is broken. So I cannot rely on
find_executable anymore to get the expected program!
Marc
On 09/09/15 20:20, "Brad King" wrote:
>On 09/09/2015 11:50 AM, Chuck Atkins wrote:
>> From what I can
On 09/14/2015 02:00 PM, Alan W. Irwin wrote:
> Because this find regression is against 3.1.3 from what Marc said, may
> I assume you are planning to include the fix for this regression in
> both future cmake-3.2.x and 3.3.y releases?
We may backport it for a possible 3.3.2 but there will be no
On 2015-09-14 10:51-0400 Brad King wrote:
On 09/14/2015 03:05 AM, CHEVRIER, Marc wrote:
Any news on this subject?
Chuck has had a fix in 'next' for a few days:
find_*: Fix search order when the environment duplicates some HINTS
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ec8e5fb3
>From what I can tell, the search order is still preserved as expected.
[chuck.atkins@hal9000 testdir]$ cat TestFindProgram.cmake
set(CMAKE_PREFIX_PATH
"/FOODIR_CMAKE_PREFIX_PATH1;/FOODIR_CMAKE_PREFIX_PATH2"
CACHE STRING "" FORCE)
set(CMAKE_PROGRAM_PATH
On 09/03/2015 03:51 AM, CHEVRIER, Marc wrote:
> 1. Build phase. Under find_program.BUG/build, use CMakeLists.txt to prepare
> runtime part
> 2. Test phase. Under find_program.BUG/runtime, use CMakeLists.txt to show the
> bug.
Thanks, Marc.
Chuck, this was regressed by your changes in CMake