Re: [CMake] Compiling fortran

On 2007-09-25 22:37-0500 John Doe wrote: While the cmake man page does not document the proper capitalization of Fortran for creating a fortran based project, I am now at the point the compilation does not work for another reason. Does anyone have an idea what this means? Clearing

Re: [CMake] Compiling fortran

On Wednesday 26 September 2007 04:37:33 [EMAIL PROTECTED] wrote: While the cmake man page does not document the proper capitalization of Fortran for creating a fortran based project, I am now at the point the compilation does not work for another reason. Does anyone have an idea what this

Re: [CMake] Question about CMAKE_INSTALL_PREFIX

Dizzy wrote: So, do you have the target file /KM/usr/ziegler/ExGen/cmake/build/src/CMakeFiles/CMakeRelink.dir/startCompletionServer ? In src/, I have the target ADD_EXECUTABLE(startCompletionServer StartCompletionServer.cpp ${BASEFILES}) If yes do you have write privileges in

Re: [CMake] Question about CMAKE_INSTALL_PREFIX

Dizzy wrote: In what way it is not used correctly? Do you set it from within CMakeLists.txt? Because that doesn't work. You can set it externally with -D Yes, in CMakeLists.txt. to cmake command line tho (similar to how you could give --prefix to configure of autoconf). OK, that works.

Re: [CMake] cmake 2.5 with windows mobile

Hello Alex, thanks for the help. Alexander Neundorf wrote: Why doesn't it work with vcvarsall.bat ? I tried today once again and it does work with vcvarsall.bat. With -D you are setting cmake variables, so they should have cmake-style paths, i.e. using forward slashes. This should fix

Re: [CMake] CPack option naming and deb generator

2007/9/26, Fredrik Hultin [EMAIL PROTECTED]: Hi I've got a question and/or suggestion regarding CPack: How are the generator specific settings supposed to be sent to the generators? If I understand the CPack system correctly you're supposed (or at least you have the option) to write CPack

[CMake] Why are object files built several times?

Hello, I have two targets that have nearly the same sources: ADD_EXECUTABLE(startCompletionServer StartCompletionServer.cpp ${BASEFILES}) ADD_EXECUTABLE(test-adler32 test-adler32.cpp ${BASEFILES}) I wonder why every object file belonging to the BASEFILES is built twice, once for the first

Re: [CMake] Why are object files built several times?

On Wednesday 26 September 2007 14:55:52 Joachim Ziegler wrote: Hello, I have two targets that have nearly the same sources: ADD_EXECUTABLE(startCompletionServer StartCompletionServer.cpp ${BASEFILES}) ADD_EXECUTABLE(test-adler32 test-adler32.cpp ${BASEFILES}) I wonder why every object file

Re: [CMake] ctest question

2007/9/25, Juan Sanchez [EMAIL PROTECTED]: Hi Alan, I also have floating point results I want to account for. I'm thinking about writing a diff script for numerical results which uses an absolute and relative error tolerance. This would account for the difference in transcendentals and

Re: [CMake] ctest question

2007/9/25, Juan Sanchez [EMAIL PROTECTED]: Hi Alan, I also have floating point results I want to account for. I'm thinking about writing a diff script for numerical results which uses an absolute and relative error tolerance. This would account for the difference in transcendentals and

Re: [CMake] Why are object files built several times?

On 26.09.07 15:13:38, Dizzy wrote: On Wednesday 26 September 2007 14:55:52 Joachim Ziegler wrote: Hello, I have two targets that have nearly the same sources: ADD_EXECUTABLE(startCompletionServer StartCompletionServer.cpp ${BASEFILES}) ADD_EXECUTABLE(test-adler32 test-adler32.cpp

Re: [CMake] Why are object files built several times?

Andreas Pakulat wrote: On 26.09.07 15:13:38, Dizzy wrote: On Wednesday 26 September 2007 14:55:52 Joachim Ziegler wrote: Hello, I have two targets that have nearly the same sources: ADD_EXECUTABLE(startCompletionServer StartCompletionServer.cpp ${BASEFILES})

Re: [CMake] CPack MacOSX bundle

On 9/25/07 12:06 PM, Félix C. Morency said: I'm trying to create a MacOSX bundle with my application. So far, everything is working (.dmg generation) except the fact that the application is always installed in /usr/bin. Is there any way to install it in the application menu ? I'm far from being a

[CMake] CMake with MinGW = .def and lib files

Hi All, I'm using CMake on Windows with a mingw compiler. I wanted to produce .def (and .lib) files corresponding to my DLL in order to be enable my user using MSVC to use the DLL as explained here: http://www.mingw.org/mingwfaq.shtml#faq-msvcdll For now I have added line likes this:

Re: [CMake] Compiling fortran

It turns out that any word of the word Use or use as a word anywhere in a comment causes the dependency scanner to use the next token on the line as a module dependency. So I changed all the code to use xUse and xuse. Thanks, Juan Alin M Elena wrote: On Wednesday 26 September 2007 04:37:33

Re: [CMake] ctest question

Awesome. I love that guys work on bibtex and bibtools. Juan Mathieu MARACHE wrote: 2007/9/25, Juan Sanchez [EMAIL PROTECTED]: Hi Alan, I also have floating point results I want to account for. I'm thinking about writing a diff script for numerical results which uses an absolute and

Re: [CMake] CPack MacOSX bundle

On 9/25/07 12:06 PM, Félix C. Morency said: I'm trying to create a MacOSX bundle with my application. So far, everything is working (.dmg generation) except the fact that the application is always installed in /usr/bin. Is there any way to install it in the application menu ? I'm far from being a

Re: [CMake] CPack MacOSX bundle

Thank you for answering. I googled the NSStatusItem and I'm not quite sure I understand what you mean. I guess putting the application in the Finder/Application menu could be done without modifying the source code ? I want to put a shortcut/the application to the bundle automaticaly with the

Re: [CMake] CPack MacOSX bundle

Sean McBride wrote: On 9/25/07 12:06 PM, Félix C. Morency said: I'm trying to create a MacOSX bundle with my application. So far, everything is working (.dmg generation) except the fact that the application is always installed in /usr/bin. Is there any way to install it in the application

Re: [CMake] when are variables inherited?

I still don't understand when variables are inherited by subdirectories. I see that if I define the variable using cmake -D then it is the same in all subdirectories. I guess I could use an environment variable. However, if I do something like: SET (FINITO_INSTALL_DIR

Re: [CMake] when are variables inherited?

hah! I see what happened. Obviously, the variable needs to be set _before_ using ADD_SUBDIRECTORY (oops). For some reason I had it after. Thanks anyway. Javier Yes, ADD_SUBDIRECTORY processes immediatly the subdirectory. Note that inherited variables actually are new variables, so if you

Re: [CMake] Compiling fortran

Hi Bill, I wouldn't mind taking a stab at it. It would be easy enough to tell lex to drop any line starting with a comment character. Something along the lines of: ^[cC].* {} There seems to be a line in the lexer that does this, but it doesn't appear that that the start condition, fixed_fmt,

Re: [CMake] Compiling fortran

Juan Sanchez wrote: It turns out that any word of the word Use or use as a word anywhere in a comment causes the dependency scanner to use the next token on the line as a module dependency. So I changed all the code to use xUse and xuse. The problem is well known, and much talked about. The

Re: [CMake] Compiling fortran

Juan Sanchez wrote: Hi Bill, I wouldn't mind taking a stab at it. It would be easy enough to tell lex to drop any line starting with a comment character. Something along the lines of: ^[cC].* {} There seems to be a line in the lexer that does this, but it doesn't appear that that the start

Re: [CMake] generating code from compiled program

Has anyone any examples of building a compiler (of sorts) and using that compiler to generate code then integrated into another CMake target? Thanks, James James Bigler wrote: I have a program built within CMake that generates some code. I need this generated code to compile some other

Re: [CMake] Compiling fortran

Anyone know what are the valid comment lines in all the Fortran variants? I know of lines beginning with c, C, or * in the first column. Juan Bill Hoffman wrote: Juan Sanchez wrote: Hi Bill, I wouldn't mind taking a stab at it. It would be easy enough to tell lex to drop any line starting

Re: [CMake] Compiling fortran

Am Mittwoch, 26. September 2007 17:34:38 schrieb Bill Hoffman: A lex/yacc guru would be best to help out here. Basically we want the fortran parser to ignore all comment lines. I gave it a try a while ago, but did not get it to work. I suppose a hack solution would be to pre-process the

[CMake] CTest and Makefiles

I have a strange problem using CTest with Makefiles. If I run make test, ctest is never called. If I change the name of the target in the Makefile from test to test2 and run make test2, then ctest is called properly. After changing the target name, make test is still recognized as a valid

Re: [CMake] CTest and Makefiles

Would you happen to have a file named test in your binary area? Make will see the file and think that the target test is up to date. A proper gnu makefile would mark the test target as phony. Looking at the gnu makefile generated by one of my projects, test is not marked as phony. Let me know

Re: [CMake] CTest and Makefiles

As a followup. If I touch test, the test no longer runs. If I add the PHONY target to the Makefile. The tests still run. ~/bar make test Running tests... Start processing tests Test project /home/juans/bar 1/ 1 Testing foo Passed 100% tests passed, 0 tests

Re: [CMake] CTest and Makefiles

Juan, Thanks for the tip! Although I did not have a file named test, I did have a directory named test (that contains all of my test projects naturally). Marking the test target as phony in the Makefile resolved the issue. It sounds like this should be fixed in the Makefile generator. There

Re: [CMake] CTest and Makefiles

I preemptively filed bug: http://www.cmake.org/Bug/view.php?id=5785 I didn't know directories could trigger this as well. Juan KSpam wrote: Juan, Thanks for the tip! Although I did not have a file named test, I did have a directory named test (that contains all of my test projects

Re: [CMake] generating code from compiled program

On 26.09.07 10:03:08, James Bigler wrote: Has anyone any examples of building a compiler (of sorts) and using that compiler to generate code then integrated into another CMake target? Look at Qt apps that use cmake and dbus. Or any kde application and KDE's automoc-compiler. Andreas -- Your

Re: [CMake] generating code from compiled program

On Sep 26, 2007, at 10:11 AM, Juan Sanchez wrote: Hello James, I'm curious why your target name is ExtractSymbolsFromXML, but your dependency is ${ExtractSymbolsFromXML_exe}. Shouldn't your dependency be the name of the target? I tried both, and neither work. In addition, if you add a

Re: [CMake] generating code from compiled program

On Sep 26, 2007, at 11:03 AM, Andreas Pakulat wrote: On 26.09.07 10:03:08, James Bigler wrote: Has anyone any examples of building a compiler (of sorts) and using that compiler to generate code then integrated into another CMake target? Look at Qt apps that use cmake and dbus. Or any kde

Re: [CMake] Compiling fortran

Maik Beckmann wrote: Am Mittwoch, 26. September 2007 17:34:38 schrieb Bill Hoffman: A lex/yacc guru would be best to help out here. Basically we want the fortran parser to ignore all comment lines. I gave it a try a while ago, but did not get it to work. I suppose a hack solution would

Re: [CMake] generating code from compiled program

On 26.09.07 11:25:21, James Bigler wrote: On Sep 26, 2007, at 11:03 AM, Andreas Pakulat wrote: On 26.09.07 10:03:08, James Bigler wrote: Has anyone any examples of building a compiler (of sorts) and using that compiler to generate code then integrated into another CMake target? Look at Qt

Re: [CMake] generating code from compiled program

Andreas Pakulat wrote: On 26.09.07 10:03:08, James Bigler wrote: Has anyone any examples of building a compiler (of sorts) and using that compiler to generate code then integrated into another CMake target Does this help: http://www.cmake.org/Wiki/CMake_FAQ See :How can I

Re: [CMake] generating code from compiled program

Bill Hoffman wrote: Andreas Pakulat wrote: On 26.09.07 10:03:08, James Bigler wrote: Has anyone any examples of building a compiler (of sorts) and using that compiler to generate code then integrated into another CMake target Does this help: http://www.cmake.org/Wiki/CMake_FAQ

[CMake] include directories variable?

How do I get the INCLUDE_DIRECTORIES path? I need to feed into into the search path for the swig command line. Thanks, Juan ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

[CMake] Project Grouping in a solution

Is there a way to group projects in a solution? Something like this would be handy CMakeProject -- ALL_BUILD -- ZERO_CHECK etc lib -- lib1 -- lib2 Possibly something that follows the file system setup. -Neal ___ CMake mailing

[CMake] Passing lists to macros

I've got the following in my CMakeLists.txt SET( L1 *.h *.hpp *.cpp *.c ) MESSAGE( STATUS L1 = ${L1} ) macro( test L2 ) MESSAGE( STATUS L2 = ${L2} ) FOREACH( L ${L2} ) MESSAGE( STATUS L = ${L} ) SET( L_LIST ${L_LIST} stuff/${L} ) ENDFOREACH( L ) MESSAGE( STATUS L_LIST = ${L_LIST} )

Re: [CMake] Passing lists to macros

Try: test(${L1}) You are passing multiple arguments to the macro by using ${L1} without double quotes (because it expands to a list with multiple elements). Using double quotes makes it all go into the first macro argument... Alternatively, you could look up the help for MACRO using: cmake

[CMake] Interresting dependency problem

Hi, I have a particular situation that I would like you to analyze to help me find the best solution possible. I have a project A, a project B and an external dependency called C. The project B depends directly on C. The project A needs the projects B to build but does not want to know about its