On 08/25/2015 01:45 AM, Rolf Eike Beer wrote:
The BZIP2_NEED_PREFIX check generates a CMakeLists.txt file that
refers to the raw path given without re-escaping the backslashes.
Then the check fails to configure due to the backslashes being
interpreted as invalid CMake escape sequences.
No,
On 08/23/2015 07:36 AM, Rolf Eike Beer wrote:
you introduced in 7c912af2 that this module not only looks into the Windows
registry, but also added PATH_SUFFIXES include and lib for find_* calls.
Wouldn't CMake automatically append those to all paths given?
No. The suffixes are only added
Brad King wrote:
On 08/23/2015 07:36 AM, Rolf Eike Beer wrote:
Another thing which I found is that there seems to be an obscure problem
in FindBZip2.cmake to not find the library on Windows if the path contains
backslashes. Yes, really. Just compare the cmake part of these 2 links (no
Brad,
you introduced in 7c912af2 that this module not only looks into the Windows
registry, but also added PATH_SUFFIXES include and lib for find_* calls. Am I
gettings something wrong? Wouldn't CMake automatically append those to all
paths given?
Another thing which I found is that there
