Re: [CMake] ccmake command missing from 3.12.0 RC releases

Thanks! On Mon, 2 Jul 2018 at 16:40, Brad King wrote: > On 07/02/2018 08:43 AM, Robert Maynard wrote: > > On Sun, Jul 1, 2018 at 6:18 PM Miklos Espak wrote: > >> the 'ccmake' command seems to be missing from the linux tarballs > >> from 3.12.0 RC1 and RC2. Not sure if you are aware of that. > >

Re: [CMake] ccmake command missing from 3.12.0 RC releases

On 07/02/2018 08:43 AM, Robert Maynard wrote: > On Sun, Jul 1, 2018 at 6:18 PM Miklos Espak wrote: >> the 'ccmake' command seems to be missing from the linux tarballs >> from 3.12.0 RC1 and RC2. Not sure if you are aware of that. > > Thanks for reporting this. I am looking into it. Thanks for the

Re: [CMake] ccmake command missing from 3.12.0 RC releases

Thanks for reporting this. I am looking into it. On Sun, Jul 1, 2018 at 6:18 PM Miklos Espak wrote: > > Hi, > > the 'ccmake' command seems to be missing from the linux tarballs from 3.12.0 > RC1 and RC2. Not sure if you are aware of that. > > The release notes does not mention that it should be

[CMake] ccmake command missing from 3.12.0 RC releases

Hi, the 'ccmake' command seems to be missing from the linux tarballs from 3.12.0 RC1 and RC2. Not sure if you are aware of that. The release notes does not mention that it should be removed, so I hope the final release is going to have it. :) Maybe the curses dev package isn't installed on the

Re: [CMake] CCMake is not getting updated

Perfect!! Now everything is working correctly!! Thank you so much!! Regards, Ana 2016-06-09 14:08 GMT+01:00 Domen Vrankar : > > And now? Do I have to uninstall cmake 3.5 and install it again? > > Rebuild (in such cases I usually remove previous build dir as in the >

Re: [CMake] CCMake is not getting updated

> And now? Do I have to uninstall cmake 3.5 and install it again? Rebuild (in such cases I usually remove previous build dir as in the past sometimes it did not detect if a new library was added to the environment) and install (install is a dumb command that only copies files so you don't need to

Re: [CMake] CCMake is not getting updated

OK, thank you very much! And now? Do I have to uninstall cmake 3.5 and install it again? Regards 2016-06-09 13:31 GMT+01:00 Domen Vrankar : > > Now I have the right version of cmake (3.5.2), but the ccmake version is > > still 2.8.12... How can I update ccmake too? > >

Re: [CMake] CCMake is not getting updated

> Now I have the right version of cmake (3.5.2), but the ccmake version is > still 2.8.12... How can I update ccmake too? Not 100% certain but my guess would be that you are missing ncurses-devel package and therefore ccmake was not built. sudo yum install ncurses-devel Regards, Domen --

[CMake] CCMake is not getting updated

Hello! I had to update cmake version from 2.8.12 to 3.5.2. I followed the steps here: https://xinyustudio.wordpress.com/2014/06/18/how-to-install-cmake-3-0-on-centos-6-centos-7/ . Now I have the right version of cmake (3.5.2), but the ccmake version is still 2.8.12... How can I update ccmake

[cmake-developers] [CMake 0014973]: [RFE] Produce shorted output for cmake/ccmake when no arguments specified

shorted output for cmake/ccmake when no arguments specified Description: Please find attached patch. Currently running cmake/ccmake without arguments is equal running it with --help which is bad idea since it doesn't really tell what to do. Instead of that attached patch makes them emit shorter

Re: [CMake] ccmake: command not found installing ITK

Am Mittwoch, 26. März 2014, 11:29:12 schrieb Zhao Long: hello, everyone, i encounter a problem and i need your help I install cmake for installing ITK in centos6.5. so i download cmake2.8.12 from cmake website,then tar it. according to the teaching, run ./bootstrap make make install. then

[CMake] ccmake: command not found installing ITK

hello, everyone, i encounter a problem and i need your help I install cmake for installing ITK in centos6.5. so i download cmake2.8.12 from cmake website,then tar it. according to the teaching, run ./bootstrap make make install. then check cmake --version,the result is cmake version 2.8.8

[CMake] Building cmake: ccmake not built

Hi all; I'm tring to build cmake using a cross-compiler environment so cmake itself will run on a different platform. It's working well, except that ccmake is not getting compiled (neither is cmake-gui but that's OK). I do have curses libraries installed and other curses programs are built and

Re: [CMake] ccmake is not getting installed

2013/1/28 Pradeep Jha pradeep.kumar@gmail.com: Hello, thank you for your replies. I mentioned in previous email that I tried this command already and this is what I am getting as output: [root@83 ~]# yum install

Re: [CMake] ccmake is not getting installed

Hello, I installed cmake without ncurses. It is version 2.8.10.2 and CentOS 5.4 --- [root@83 cmake-2.8.10.2]# cmake --version cmake version 2.8.10.2 [root@83 ~]# cat /etc/redhat-release CentOS release 5.4 (Final)

Re: [CMake] ccmake is not getting installed

2013/1/29 Pradeep Jha pradeep.kumar@gmail.com: Hello, I installed cmake without ncurses. It is version 2.8.10.2 and CentOS 5.4 --- [root@83 cmake-2.8.10.2]# cmake --version cmake version 2.8.10.2

Re: [CMake] ccmake is not getting installed

Hello, I have attached the cmake-run.out file with this email. Also the output for all the commands that you suggested is attached below. Thanks --- [root@83 build]# /usr/local/bin/cmake ./../cmake-2.8.10.2 Curses

Re: [CMake] ccmake is not getting installed

On 1/29/2013 4:06 AM, Pradeep Jha wrote: Hello, I have attached the cmake-run.out file with this email. Also the output for all the commands that you suggested is attached below. You are missing the header files for curses, not the libraries. You need the headers to compile against the

Re: [CMake] ccmake is not getting installed

Hello, I do have the ncurses.h file - [root@83 cmake-2.8.10.2]# locate ncurses.h /usr/include/ncurses.h /usr/include/ncurses/ncurses.h /usr/include/ncursesw/ncurses.h

Re: [CMake] ccmake is not getting installed

On 1/29/2013 10:29 AM, Pradeep Jha wrote: Hello, I do have the ncurses.h file Can you run cmake like this and send me the log. (off the list it will be big.) cmake -DCMAKE_FIND_DEBUG_MODE=TRUE --trace -- Bill Hoffman Kitware, Inc. 28 Corporate Drive Clifton Park, NY 12065

Re: [CMake] ccmake is not getting installed

On Jan 29, 2013, at 10:38 AM, Bill Hoffman bill.hoff...@kitware.com wrote: On 1/29/2013 10:29 AM, Pradeep Jha wrote: Hello, I do have the ncurses.h file Can you run cmake like this and send me the log. (off the list it will be big.) cmake -DCMAKE_FIND_DEBUG_MODE=TRUE --trace --

Re: [CMake] ccmake is not getting installed

On 1/29/2013 8:56 PM, Pradeep Jha wrote: I printed both CURSES_NCURSES_LIBRARY AND NOT CURSES_CURSES_LIBRARY and they were respectively /usr/lib64/libncurses.so.5 and /usr/lib64/libcurses.so and so the variable CURSES_USE_NCURSES was set to False. I didnt know what to do so I forced the last

[CMake] ccmake is not getting installed

Hello, I am trying to install the latest version of cmake on my centos linux machine. [root@83 lib64]# uname -a Linux 83.shin.fluid.cse.nagoya-u.ac.jp 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

Re: [CMake] ccmake is not getting installed

Am Montag, 28. Januar 2013 um 09:15:58, schrieb Pradeep Jha pradeep.kumar@gmail.com When I run the bootsrap command, it executes it successfully but gives me the following message at the end: Curses libraries were not found. Curses GUI for CMake will not be built. To compile, you

Re: [CMake] ccmake is not getting installed

2013/1/28 Kornel Benko kor...@lyx.org: Am Montag, 28. Januar 2013 um 09:15:58, schrieb Pradeep Jha pradeep.kumar@gmail.com When I run the bootsrap command, it executes it successfully but gives me the following message at the end: Curses libraries were not found. Curses GUI for

Re: [CMake] ccmake is not getting installed

Eric Noulard eric.noulard@... writes: 2013/1/28 Kornel Benko kornel@...: Am Montag, 28. Januar 2013 um 09:15:58, schrieb Pradeep Jha pradeep.kumar.jha@... When I run the bootsrap command, it executes it successfully but gives me the following message at the end: Curses

Re: [CMake] ccmake was not created

Hi all! Good news - ccmake was created, but for the previous stable version (2.6.4). I still didn't understand what is the problem with ccmake in the last version (2.8.6). Best regards, Mikhail -- Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [CMake] ccmake was not created

On 11/22/2011 09:28 AM, Mikhail Artemiev wrote: I don't see a BUILD_CursesDialog entry in my CMakeCache.txt file.But a CURSES_NCURSES_LIBRARY entry exists, and it point to /usr/lib/libncurses.so (which exists too).When I try to add a string BUILD_CursesDialog:BOOL=ON intoCMakeCache.txt by hand

Re: [CMake] ccmake was not created

In your bootstrap log, do you see something like the following? Curses libraries were not found. Curses GUI for CMake will not be built. Yes. But I don't understand. The curses library was installed. My LD_LIBRARY_PATH is $echo $LD_LIBRARY_PATH /usr/lib What's wrong? Mikhail -- Powered by

Re: [CMake] ccmake was not created

On 11/22/2011 10:58 AM, Mikhail Artemiev wrote: In your bootstrap log, do you see something like the following? Curses libraries were not found. Curses GUI for CMake will not be built. Yes. But I don't understand. The curses library was installed. My LD_LIBRARY_PATH is $echo

Re: [CMake] ccmake was not created

Hello! Thank you for the help. Here is a part of my CMakeCashe.txt: // --- //Path to a file. CURSES_CURSES_H_PATH:PATH=/usr/include //Path to a library. CURSES_CURSES_LIBRARY:FILEPATH=/usr/lib/libcurses.so //Path to a library.

[CMake] ccmake was not created

Hello! After configuring (./configure --prefix=/home/mikhail/install), building (make) and installation (make install) of CMake 2.8.6, I don't have ccmake in /home/mikhail/install/bin directory. What I'm doing wrong? Or I need additional sources for ccmake? My OS is Ubuntu 10.04. Thanks in

Re: [CMake] ccmake was not created

On 11/22/2011 06:45 AM, Mikhail Artemiev wrote: Hello! After configuring (./configure --prefix=/home/mikhail/install), building (make) and installation (make install) of CMake 2.8.6, I don't have ccmake in /home/mikhail/install/bin directory. What I'm doing wrong? Or I need additional

Re: [CMake] ccmake was not created

Hi Michael! Thank you for the quick reply. I didn't have this library. Now I installed it, then I reconfigured, rebuild and reinstalled CMake, but still I didn't find ccmake nowhere. Mikhail -- Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [CMake] ccmake was not created

On 11/22/2011 08:34 AM, Mikhail Artemiev wrote: Hi Michael! Thank you for the quick reply. I didn't have this library. Now I installed it, then I reconfigured, rebuild and reinstalled CMake, but still I didn't find ccmake nowhere. Mikhail Do you see a BUILD_CursesDialog entry in your

Re: [CMake] ccmake was not created

I don't see a BUILD_CursesDialog entry in my CMakeCache.txt file.But a CURSES_NCURSES_LIBRARY entry exists, and it point to /usr/lib/libncurses.so (which exists too).When I try to add a string BUILD_CursesDialog:BOOL=ON intoCMakeCache.txt by hand and then remake the project,CMakeCache.txt

Re: [CMake] ccmake options organization

On Mon, Jun 13, 2011 at 6:23 PM, Bill Hoffman bill.hoff...@kitware.com wrote: On 6/13/2011 11:02 AM, Szilárd Páll wrote: I would also very much like to see some form of grouping to be possible in ccmake. Right now, the only way to avoid clutter is to mark the large majority of the variables

Re: [CMake] ccmake options organization

On Friday 10 June 2011, Tim Gallagher wrote: Hi all, We have a code that has a lot of options to enable/disable at compile time, and we'd also like to use ccmake to generate input files to run the code (possibly several hundred options combined). But the way the curses gui organizes things

Re: [CMake] ccmake options organization

and if our guys are just lazy/crazy :) Tim - Original Message - From: Michael Wild them...@gmail.com To: cmake@cmake.org Sent: Monday, June 13, 2011 6:09:07 AM Subject: Re: [CMake] ccmake options organization On 06/13/2011 11:01 AM, Alexander Neundorf wrote: On Friday 10 June 2011, Tim

Re: [CMake] ccmake options organization

Message - From: Michael Wild them...@gmail.com To: cmake@cmake.org Sent: Monday, June 13, 2011 6:09:07 AM Subject: Re: [CMake] ccmake options organization On 06/13/2011 11:01 AM, Alexander Neundorf wrote: On Friday 10 June 2011, Tim Gallagher wrote: Hi all, We have a code that has a lot

Re: [CMake] ccmake options organization

On 6/13/2011 11:02 AM, Szilárd Páll wrote: I would also very much like to see some form of grouping to be possible in ccmake. Right now, the only way to avoid clutter is to mark the large majority of the variables as advanced and keep only the ones that would be used frequently used and this is

[CMake] ccmake options organization

Hi all, We have a code that has a lot of options to enable/disable at compile time, and we'd also like to use ccmake to generate input files to run the code (possibly several hundred options combined). But the way the curses gui organizes things makes it really hard/tedious to keep track of

Re: [CMake] ccmake options organization

Hi, I have run into the same trouble and I've started on a local branch to add a filter option to ccmake as well as others improvement. As you probably know the cmake GUI already provides such options. Cheers, -Nico On Fri, Jun 10, 2011 at 7:29 PM, Tim Gallagher tim.gallag...@gatech.edu wrote:

Re: [CMake] ccmake and cmake

2010/9/24 Michael Wild them...@gmail.com: Oh, wow, hardy is REALLY, *REALLY* old. It still contains only cmake-2.4.7 which was released more than 3 years ago! I would recommend downloading a pre-built binary. It is self-contained and you can just drop it anywhere you want (e.g. somewhere

Re: [CMake] ccmake and cmake

With Ubuntu you need the cmake-curses-gui package. Michael On 23. Sep, 2010, at 24:25 , David Cole wrote: If you have cmake, you have ccmake. They are not installed separately. ccmake is part of the cmake package. On Wed, Sep 22, 2010 at 6:22 PM, Siddharth Srivastava

Re: [CMake] ccmake and cmake

Thanks all, for the replies... I now know that I need to install cmake-curses-gui. However (on my Ubuntu hardy) apt-get does not find this package. Do I have to specify a repository in my sources.list where it can find this package? I am also ready to compile from source, if that is the only

Re: [CMake] ccmake and cmake

Oh, wow, hardy is REALLY, *REALLY* old. It still contains only cmake-2.4.7 which was released more than 3 years ago! I would recommend downloading a pre-built binary. It is self-contained and you can just drop it anywhere you want (e.g. somewhere in your home directory) and simply update your

[CMake] ccmake and cmake

Hi everyone, Just joined the list. How can I tell ccmake to use a specific version of cmake? I have 2.4.7, 2.8.1 and 2.8.2 installed, and I wanted to use 2.8.2. Can I specify this on the command line? Thanks, sid. ___ Powered by www.kitware.com

Re: [CMake] ccmake and cmake

On 9/22/2010 4:13 PM, Siddharth Srivastava wrote: Hi everyone, Just joined the list. How can I tell ccmake to use a specific version of cmake? I have 2.4.7, 2.8.1 and 2.8.2 installed, and I wanted to use 2.8.2. Can I specify this on the command line? Thanks, sid. Each cmake comes with

Re: [CMake] ccmake and cmake

Hi Ryan, Thanks. Where can i download the latest binary from? I searched and was only able to find binaries for cmake. if there is an apt-get way to do it, that would be great! sid. On Wed, Sep 22, 2010 at 3:10 PM, Ryan Pavlik rpav...@iastate.edu wrote: On 9/22/2010 4:13 PM, Siddharth

Re: [CMake] ccmake and cmake

If you have cmake, you have ccmake. They are not installed separately. ccmake is part of the cmake package. On Wed, Sep 22, 2010 at 6:22 PM, Siddharth Srivastava sid...@gmail.comwrote: Hi Ryan, Thanks. Where can i download the latest binary from? I searched and was only able to find

Re: [CMake] ccmake .

Tested with cmake 2.6.4 on linux. It is the case with all my projects, probably we don't need a test case. The mentioned actions simply modify CMakeCache.txt (check with your running projects), while they should not, should they? Dominik Eric Noulard wrote: 2009/8/13 Dominik Szczerba

Re: [CMake] ccmake .

I also noticed that ccmake always modifies the cache. But that in itself should NOT cause a complete rebuild of your project. On the next `make' it should only re-configure and regenerate the build system, and then print a list of all targets as Make checks them all, but nothing should

Re: [CMake] ccmake .

2009/8/14 Michael Wild them...@gmail.com: I also noticed that ccmake always modifies the cache. But that in itself should NOT cause a complete rebuild of your project. On the next `make' it should only re-configure and regenerate the build system, and then print a list of all targets as Make

Re: [CMake] ccmake .

Filed under: http://public.kitware.com/Bug/view.php?id=9418 Many thanks Eric and Michael. PS. Indeed, cmake-gui does NOT modify the cache in vein, which is what I would expect. Dominik Eric Noulard wrote: 2009/8/14 Michael Wild them...@gmail.com: I also noticed that ccmake always

[CMake] ccmake .

Once again: I am calling 'ccmake .', 'cmake-gui.' or 'make edit_cache' just to inspect the build settings. I quit with no changes saved. Then 'make' rebuilds the project, which is an obvious bug or *extremely* unexpected behavior. -- d o m i n i k s z c z e r b a , p h d . . . . . . . . . .

Re: [CMake] ccmake .

2009/8/13 Dominik Szczerba domi...@itis.ethz.ch: Once again: I am calling 'ccmake .', 'cmake-gui.' or 'make edit_cache' just to inspect the build settings. I quit with no changes saved. Then 'make' rebuilds the project, which is an obvious bug or *extremely* unexpected behavior. Which CMake

Re: [CMake] ccmake gets all squirrelly over which C++ compiler to use.

So the problem with CCMake forgetting valid user input stems from the entire CMakeCache.txt file getting deleted if there's a compiler mismatch? On Tue, Mar 3, 2009 at 11:21 AM, Bill Hoffman bill.hoff...@kitware.com wrote: Mathieu Malaterre wrote: On Tue, Mar 3, 2009 at 4:20 PM, kent williams

Re: [CMake] ccmake gets all squirrelly over which C++ compiler to use.

Yeah, if you're comfortable using the Unix command line, using non-interactive CMake this way is almost always an easier path to joy than using the GUI or Curses interactive application. It's why the Slicer people spent considerable time putting together a suite of TCL scripts to do their builds,

Re: [CMake] ccmake gets all squirrelly over which C++ compiler to use.

kent williams wrote: So the problem with CCMake forgetting valid user input stems from the entire CMakeCache.txt file getting deleted if there's a compiler mismatch? Yes, that is what happens. The use case that this was supposed to address was this: ccmake ../source - oops, I did not

Re: [CMake] ccmake gets all squirrelly over which C++ compiler to use.

I have had this issue an infinite number of time. Debian packager would be using inconsistant c++ compiler and I could not use both ITK and VTK at the same time (from debian package). So I provided an (undocumented) hack: CMAKE_OVERRIDE_COMPILER_MISMATCH 2cts On Mon, Mar 2, 2009 at 8:27 PM, kent

Re: [CMake] ccmake gets all squirrelly over which C++ compiler to use.

That's all well and good, but is exactly the sort of thing I DONT want to have to put in FOSS CMakeaLists.txt files. It would be useful in situations like this where you're liking against multiple system-installed CMake-built libraries. But any other situation, you'd run into problems where a

Re: [CMake] ccmake gets all squirrelly over which C++ compiler to use.

On Tue, Mar 3, 2009 at 4:20 PM, kent williams nkwmailingli...@gmail.com wrote: Lather, Rinse, Repeat. After 2 or 3 go-arounds, CCMake is happy and lets you generate your build files. And if I recall correctly, earlier versions (2.3? 2.4?) did not act this way. Yup, this behavior appears

Re: [CMake] ccmake gets all squirrelly over which C++ compiler to use.

On Tue 2009-03-03 09:20, kent williams wrote: Lather, Rinse, Repeat. After 2 or 3 go-arounds, CCMake is happy and lets you generate your build files. This and the fact that most modules aren't written to handle multiple passes (for instance, if the wrong version is found on the first pass, the

Re: [CMake] ccmake gets all squirrelly over which C++ compiler to use.

Mathieu Malaterre wrote: On Tue, Mar 3, 2009 at 4:20 PM, kent williams nkwmailingli...@gmail.com wrote: Lather, Rinse, Repeat. After 2 or 3 go-arounds, CCMake is happy and lets you generate your build files. And if I recall correctly, earlier versions (2.3? 2.4?) did not act this way. Yup,

[CMake] ccmake gets all squirrelly over which C++ compiler to use.

Version 2.6 patch 2 on OS X and Linux -- you know your code is portable when the same issue happens on multiple platforms! Here's the scenario -- a guy in our department was having trouble getting ccmake to generate makefiles. My diagnosis was pretty simple: His project depended on both ITK and

[CMake] ccmake not built on Linux 64

Just tried building cmake from source on Linux X86_64 (KUbuntu running inside Sun's Virtual Box environment. The only thing that got built was cmake, cpack and ctest. Where is ccmake at? I looked through the ./ configure --help and nothing really jumped out at me. Thanks

Re: [CMake] ccmake not built on Linux 64

I recently did a 64 bit ubuntu cmake build and had the same outcome. I installed curses (from package I think) then ccmake built for me. On Tue, Feb 17, 2009 at 3:21 PM, Michael Jackson mike.jack...@bluequartz.net wrote: Just tried building cmake from source on Linux X86_64 (KUbuntu running

Re: [CMake] ccmake not built on Linux 64

I recently did a 64 bit ubuntu cmake build and had the same outcome. I installed curses (from package I think) then ccmake built for me. make that ncurses 5.7 built from source. On Tue, Feb 17, 2009 at 3:21 PM, Michael Jackson mike.jack...@bluequartz.net wrote: Just tried building cmake

Re: [CMake] ccmake not built on Linux 64

Yep. Silly me, expecting ncurses to be installed by default.. --- Mike Jackson www.bluequartz.net On Feb 17, 2009, at 3:25 PM, David E DeMarle wrote: I recently did a 64 bit ubuntu cmake build and had the same outcome. I installed curses (from package I think) then ccmake

Re: [CMake] ccmake not built on Linux 64

I'll try that. I just did the apt-get thing to install the libncurses5- dev package and the cmake boot strapper still can not find the curses library. --- Mike Jackson www.bluequartz.net On Feb 17, 2009, at 3:27 PM, David E DeMarle wrote: I recently did a 64 bit ubuntu

Re: [CMake] ccmake not built on Linux 64

2009/2/17 Michael Jackson mike.jack...@bluequartz.net: I'll try that. I just did the apt-get thing to install the libncurses5-dev package and the cmake boot strapper still can not find the curses library. I do build CMake 2.6-patch 3 RC-13 on Debian Lenny amd64 and ccmake did build fine.

[CMake] ccmake of HEAD is brocken

martink made some changes of the documentation implementation and it seems he didn't applied those changes to Source/CursesDialog/ccmake.cxx I fixed my build by looking at the diffs and doing a bunch of find 0 replace with action on ccmake.cxx . Regards, Maik Beckmann

[CMake] ccmake not compiled in kubuntu, please help

hi, all I got the problem that the ccmake was not compiled in the kubuntu (a kde debian version). What else library should I install to make the ccmake available? It says curses library needed for the ccmake but I don't know what are the exact name of the librarys in kubuntu. I have ncurses-base,

Re: [CMake] ccmake not compiled in kubuntu, please help

[EMAIL PROTECTED] wrote: hi, all I got the problem that the ccmake was not compiled in the kubuntu (a kde debian version). What else library should I install to make the ccmake available? It says curses library needed for the ccmake but I don't know what are the exact name of the librarys in

Re: [CMake] ccmake not compiled in kubuntu, please help

Quoting [EMAIL PROTECTED]: hi, all I got the problem that the ccmake was not compiled in the kubuntu (a kde debian version). What else library should I install to make the ccmake available? It says curses library needed for the ccmake but I don't know what are the exact name of the librarys in

Re: [CMake] ccmake and fortran

At 10:17 AM 8/17/2006, [EMAIL PROTECTED] wrote: William A. Hoffman [EMAIL PROTECTED] wrote: OK, I am going to revert my changes. It causes the lex to go into an infinite loop and I don't have time to track it down now. -Bill Were you having problems with a fixed or free formatted

Re: [CMake] ccmake and fortran

Hello all, I guess I got side-tracked about the exact nature of the problem - recognising those lines that can possibly contain dependency information - as opposed to the problem of determining comment lines ;). I am for easy, and having to specify this is difficult for cmake developers

Re: [CMake] ccmake and fortran

Brad King [EMAIL PROTECTED] wrote: FYI, there is a bug report for this problem: http://www.cmake.org/Bug/bug.php?op=showbugid=3109 I briefly looked at fixing it but got stuck on the free-format versus fixed-format parsing. Unfortunately I have no time for this bug now. Please

Re: [CMake] ccmake and fortran

At 11:48 AM 8/15/2006, [EMAIL PROTECTED] wrote: Brad King [EMAIL PROTECTED] wrote: FYI, there is a bug report for this problem: http://www.cmake.org/Bug/bug.php?op=showbugid=3109 I briefly looked at fixing it but got stuck on the free-format versus fixed-format parsing.

Re: [CMake] ccmake and fortran

William A. Hoffman [EMAIL PROTECTED] wrote: Will the change I just checked into CVS work for you? -Bill Yeah, sorry I wrote my email before seeing that you had committed a change. Bryan ___ CMake mailing list CMake@cmake.org

Re: [CMake] ccmake and fortran

[EMAIL PROTECTED] wrote: Hi Alan, My knowledgebase of fortran lies with fixed format f77 fortran, so your right the solution below only works for fixed format Fortran. There is currently nothing in the .l file to set the fixed_fmt state, so the line: fixed_fmt^[cC*dD].*\n { return EOSTMT;

Re: [CMake] ccmake and fortran

At 02:37 AM 8/14/2006, Arjen Markus wrote: [EMAIL PROTECTED] wrote: Hi Alan, My knowledgebase of fortran lies with fixed format f77 fortran, so your right the solution below only works for fixed format Fortran. There is currently nothing in the .l file to set the fixed_fmt state, so the

Re: [CMake] ccmake and fortran

William A. Hoffman wrote: Can we just have the rule for both? Basically, anything after a c should be a comment? If it is old fixed format fortran it won't have modules anyway, and should have no depends. So, if it finds too many comments because of a stray c in the code it won't hurt.

Re: [CMake] ccmake and fortran

At 10:43 AM 8/14/2006, Arjen Markus wrote: William A. Hoffman wrote: Can we just have the rule for both? Basically, anything after a c should be a comment? If it is old fixed format fortran it won't have modules anyway, and should have no depends. So, if it finds too many comments because of

Re: [CMake] ccmake and fortran

William A. Hoffman wrote: At 10:43 AM 8/14/2006, Arjen Markus wrote: William A. Hoffman wrote: Can we just have the rule for both? Basically, anything after a c should be a comment? If it is old fixed format fortran it won't have modules anyway, and should have

Re: [CMake] ccmake and fortran

At 11:05 AM 8/14/2006, Arjen Markus wrote: Can we just have the rule for both? Basically, anything after a c should be a comment? If it is old fixed format fortran it won't have modules anyway, and should have no depends. So, if it finds too many comments because of a stray c in the code it

Re: [CMake] ccmake and fortran

At 09:53 PM 8/14/2006, Alan W. Irwin wrote: An even easier solution (as proposed by Bill Hoffman) is for CMake to parse fortran files ignoring all distinctions between fixed and free format (so that any line starting with [cC*dD] is automatically skipped even though it is not a comment for the

Re: [CMake] ccmake and fortran

On 2006-08-14 22:15-0400 William A. Hoffman wrote: At 09:53 PM 8/14/2006, Alan W. Irwin wrote: An even easier solution (as proposed by Bill Hoffman) is for CMake to parse fortran files ignoring all distinctions between fixed and free format (so that any line starting with [cC*dD] is

Re: [CMake] ccmake and fortran

On 2006-08-12 07:01-0700 [EMAIL PROTECTED] wrote: My knowledgebase of fortran lies with fixed format f77 fortran, so your right the solution below only works for fixed format Fortran. There is currently nothing in the .l file to set the fixed_fmt state, so the line: fixed_fmt^[cC*dD].*\n {

Re: [CMake] ccmake and fortran

When I run ccmake and set CMAKE_Fortran_Compiler to ifort or ${Install Path}/ifort and then configure CMAKE_Fortran_Compiler resets back to the gnu compiler /usr/bin/f95. I don't understand why this is happening. Any ideas? I'm running on FC4, with CMAKE 2.4.3. Running ifort from the

Re: [CMake] ccmake and fortran

Thanks Bill that worked great! I was missing the step about deleting the cache file. The next problem that I ran into was various mod.proxy dependency issues. I saw an earlier thread on this but no solution was reached. I ended up commenting out the module dependency code under

Re: [CMake] ccmake and fortran

What I found with the module problem was that the parser was picking up the keyword in the comment. I just did something like add braces around the module keyword so that the parser was a little more confused and didn't identify the word module in the comment. Something like . . . c

Re: [CMake] ccmake and fortran

Thanks Karl, that got me looking in the right direction: Changing the line fixed_fmt^[cC*dD].*\n { return EOSTMT; } to: ^[cC*dD].*\n { return EOSTMT; } in cmDependsFortranLexer.in.y fixes the problem. This forces the parser to ignore comment lines. I also discovered that include paths are

[CMake] ccmake and fortran

Hi, I'm trying to get a mixed C++ and fortran project up and going using the Intel Fortran compiler. I have a CMakeLists.txt file that looks something like this: SET (TARGET ProjectName) PROJECT(${TARGET} CXX Fortran) SET (SRCS . . . ) ADD_LIBRARY(${TARGET} SHARED ${SRCS})

[CMake] ccmake . configure changes intel compiler selection from icc back to gcc! Why? Anyone know?

Hi all, Doing an OSX VTK build on intel core duo platform OSX10.4 Cmake 2.4 patch2 VTK CVS yesterday trying to use intel compilers for OSX intel ccmake . configure changes intel compiler selection from icc back to gcc! Why? Anyone know? also it changes icpc back to g++ icc and icpc are

Re: [CMake] ccmake . configure changes intel compiler selection from icc back to gcc! Why? Anyone know?

Dan White wrote: Hi all, Doing an OSX VTK build on intel core duo platform OSX10.4 Cmake 2.4 patch2 VTK CVS yesterday trying to use intel compilers for OSX intel ccmake . configure changes intel compiler selection from icc back to gcc! Why? Anyone know? also it changes icpc back to g++