I'm sorry but I don't quite understand the first sentence in your response.
How would I run my locally-built cmake "for the cmake sources"? Do you mean try
to use cmake to generate a makefile for the cmake sources?
Also, I don't know anything regarding cmake's trace features. I only use it to
compile other software that need cmake, like ParaView, so my cmake knowledge is
fairly limited. I do wonder if most people have ncurses in /usr/local/include
and have not run into this problem.
Sohail
________________________________
From: Andreas Pakulat <ap...@gmx.de>
To: Sohail Shafii <sohailsha...@yahoo.com>
Cc: "cmake@cmake.org" <cmake@cmake.org>
Sent: Monday, June 25, 2012 3:53 PM
Subject: Re: [CMake] Trying to compile cmake with local copy of ncurses library
Hi,
On Mon, Jun 25, 2012 at 11:48 PM, Sohail Shafii <sohailsha...@yahoo.com> wrote:
Thanks. What it is apparently doing is including the argument:
-I/home/***/local/include/ncurses. It should be -I/home/***/local/include. I'm
not sure why it generates the former during the bootstrap/configuration phase.
>
>
>
>The problem variable is the following in the CMakeCache.txt file:
>//The curses include path
>CURSES_INCLUDE_PATH:FILEPATH=/home/***/local/include/ncurses
>
>
>I had to remove "ncurses" from that line. Not a permanent solution because the
>bootstrap will just generate that line each time. It compiles with this
>custom fix though.
Does this also happen when you use your finished CMake build and run it in a
fresh builddirectory for the cmake sources? If so you could try to use cmake's
trace features to see where the value is coming from and check wether maybe the
find_path invocation for detecting the directory is wrong.
Andreas
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
