Re: [CMake] Trying to compile cmake with local copy of ncurses library

2012-06-26 Thread Andreas Pakulat
Hi,

On Tue, Jun 26, 2012 at 12:14 AM, Sohail Shafii sohailsha...@yahoo.comwrote:

 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?


Yes, exactly, use the cmake that you just built to configure a build
directory for the CMake sources. That way you can do more diagnostics than
with the bootstrap script.


 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.


Running cmake --trace normal arguments put here prints each line that
cmake evaluates as it runs through the scripts. If this doesn't answer the
question as to why it uses the wrong path, then you'd need to add some
debug-message() calls into the FindCurses.cmake script to detect where the
variables are set and to what value. If you want to debug/find the reason
for this at all.

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

Re: [CMake] Trying to compile cmake with local copy of ncurses library

2012-06-25 Thread Andreas Pakulat
Hi,

On Mon, Jun 25, 2012 at 11:25 PM, Sohail Shafii sohailsha...@yahoo.comwrote:

 Hi,

 [ 49%] Building C object
 Source/CursesDialog/form/CMakeFiles/cmForm.dir/fld_arg.c.o
 In file included from
 /home/***/src/cmake-2.8.8/Source/CursesDialog/form/form.priv.h:34,
  from
 /home/***/src/cmake-2.8.8/Source/CursesDialog/form/fld_arg.c:33:
 /home/***/src/cmake-2.8.8/Source/CursesDialog/form/form.h:46:31: error:
 ncurses/ncurses.h: No such file or directory

 This is unusual to me because in the CmakeCache text file I see the exact
 location of the file listed for the CURSES_HAVE_NCURSES_CURSES_H:FILEPATH
 variable.


When you encounter compile errors such as the above, run make VERBOSE=1 to
see what the actual compiler commandline is. If that one is missing the
path you think should be there and since your cmake is not built yet, I'd
suggest to trace down how the include-dirs for ncurses end up being given
to the target.

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

Re: [CMake] Trying to compile cmake with local copy of ncurses library

2012-06-25 Thread Sohail Shafii
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.


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:32 PM
Subject: Re: [CMake] Trying to compile cmake with local copy of ncurses library
 

Hi,


On Mon, Jun 25, 2012 at 11:25 PM, Sohail Shafii sohailsha...@yahoo.com wrote:

Hi,


[ 49%] Building C object 
Source/CursesDialog/form/CMakeFiles/cmForm.dir/fld_arg.c.o
In file included from 
/home/***/src/cmake-2.8.8/Source/CursesDialog/form/form.priv.h:34,
 from
 /home/***/src/cmake-2.8.8/Source/CursesDialog/form/fld_arg.c:33:
/home/***/src/cmake-2.8.8/Source/CursesDialog/form/form.h:46:31: error: 
ncurses/ncurses.h: No such file or directory



This is unusual to me because in the CmakeCache text file I see the exact 
location of the file listed for the CURSES_HAVE_NCURSES_CURSES_H:FILEPATH 
variable. 

When you encounter compile errors such as the above, run make VERBOSE=1 to see 
what the actual compiler commandline is. If that one is missing the path you 
think should be there and since your cmake is not built yet, I'd suggest to 
trace down how the include-dirs for ncurses end up being given to the target.

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

Re: [CMake] Trying to compile cmake with local copy of ncurses library

2012-06-25 Thread Andreas Pakulat
Hi,

On Mon, Jun 25, 2012 at 11:48 PM, Sohail Shafii sohailsha...@yahoo.comwrote:

 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

Re: [CMake] Trying to compile cmake with local copy of ncurses library

2012-06-25 Thread Sohail Shafii
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