Dear all,
I am writting cmake file to build library libVisionComponents that
includes sources from subdirectories (each subdir is different
component). In the main cmake file, sources and headers are listed as
ComponentName/File.cpp. The library is compiled successfully, but when
I install it
Doug Henry wrote:
The sun compilers also have aliases: suncc, sunCC, sunf95, etc. Maybe
those names should be used instead? I assume this is as easy as
making a Linux-sunCC.cmake file.
Will that not get you in trouble with filesystems like Windows' that do not
consider the case to be
2006/10/26, Martin Lütken [EMAIL PROTECTED]:
How can I specify the build directory from the cmake command line client?
I can do it from within the GUI, but have not been able to get cmake to
create it's make-files
in other directories than the default, which is at the source root.
In fact
I have not seen a repo for cmake files like that, but I have a feeling there are cmake build files for zlib, png, etc in the VTK source (vtk.org).On 10/25/06,
Luigi Calori [EMAIL PROTECTED] wrote:
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote: Hi, On Windows side, I built a zlib library and
Doug Henry wrote:
I have not seen a repo for cmake files like that, but I have a feeling
there are cmake build files for zlib, png, etc in the VTK source
(vtk.org http://vtk.org).
Another thing for people to do, is to request that the maintainers of
zlib, png, etc, add CMakeLists.txt files to
On 2006-10-26 09:40+0200 Eric Noulard wrote:
2006/10/26, Martin Lütken [EMAIL PROTECTED]:
How can I specify the build directory from the cmake command line client?
I can do it from within the GUI, but have not been able to get cmake to
create it's make-files
in other directories than the
Gregor Berginc wrote:
I am writting cmake file to build library libVisionComponents that
includes sources from subdirectories (each subdir is different
component). In the main cmake file, sources and headers are listed as
ComponentName/File.cpp. The library is compiled successfully, but when
Tristan Carel wrote:
To use it:
### Extract information from the current subversion working copy
INCLUDE(UseSubversion.cmake)
IF(SUBVERSION_SVN_FOUND)
SUBVERSION_REPOSITORY(${PROJECT_SOURCE_DIR})
ENDIF(SUBVERSION_SVN_FOUND)
This looks like a nice module. You should be able to convert it
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote:
Sounds like CMAKE_MODULE_PATH suggested by Alan
wouldn't do the trick.
Will this change make it for CMake 2.4.4?
I'm not sure about 2.4.4. You can check the documentation of the
FIND_PACKAGE command when it comes out. It will
On 10/26/06, Brad King [EMAIL PROTECTED] wrote:
Tristan Carel wrote:
To use it:
### Extract information from the current subversion working copy
INCLUDE(UseSubversion.cmake)
IF(SUBVERSION_SVN_FOUND)
SUBVERSION_REPOSITORY(${PROJECT_SOURCE_DIR})
ENDIF(SUBVERSION_SVN_FOUND)
This looks like
Tristan Carel wrote:
In Modules/readme.txt, in the list of variables to provide, I can read:
---
XXX_EXECUTABLE Where to find the XXX tool.
XXX_YYY_EXECUTABLE Where to find the YYY tool that comes with XXX.
---
Subversion is a set of
On 10/26/06, Brad King [EMAIL PROTECTED] wrote:
Tristan Carel wrote:
In Modules/readme.txt, in the list of variables to provide, I can read:
[...]
FindSubversion.cmake - capitalized
vs
IF(SUBVERSION_FOUND) - uppercased
[...]
For a while I was arguming that the case-ness should always
Tristan Carel wrote:
RC1 in attachment.
That looks pretty nice. Here are a few comments:
1.) Please change EXEC_PROGRAM to EXECUTE_PROCESS. You can use the new
OUTPUT_STRIP_TRAILING_WHITESPACE option in CVS CMake's EXECUTE_PROCESS
to avoid extra newlines. Since the module will not be
Sounds like CMAKE_MODULE_PATH suggested by Alan
wouldn't do the trick.
An obvious interpretation of your question (which I have just re-read) is
how could I use a private module designed for one project in another
project? If that interpretation of your question is correct, then simply
Thank You for the suggestion.
Your interpretation is right but there is a catch to it.
There is another module that gets in the way. The private
module designed for one project is zlibConfig.cmake. CMake
distribution comes with a module Findzlib.cmake. When
another project calls
On 10/26/06, Brad King [EMAIL PROTECTED] wrote:
Tristan Carel wrote:
That looks pretty nice. Here are a few comments:
1.) Please change EXEC_PROGRAM to EXECUTE_PROCESS.
Done.
You can use the new
OUTPUT_STRIP_TRAILING_WHITESPACE option in CVS CMake's EXECUTE_PROCESS
to avoid extra
Hello!
I' got a little problem which I like do describe.
Given the structure...
Project_dir:
- file: main_dummy.ccg
- file: CMakeLists.txt
- dir: mydir
mydir:
- file: CMakeLists.txt
This is an edited version of a previous post I made on the subject of the
fortran 95 module dependency issue with CMake-2.4.3. However, my previous
post was buried in another thread (in early September) and got no response
so I will try again.
Here are three files in a test source tree that
On 2006-10-26 15:38-0700 Alan W. Irwin wrote:
This is an edited version of a previous post I made on the subject of the
fortran 95 module dependency issue with CMake-2.4.3. However, my previous
post was buried in another thread (in early September) and got no response
so I will try again.
I
Hey guys,
So to warn you, this is really more of a regular _expression_
question than a cmake question but since the problem is in a cmake script I
thought you guys may cut me some slack. J In any
case, I have a situation where my source directory contains the following:
On 10/26/06, Matthew Campbell [EMAIL PROTECTED] wrote:
Hey guys,
So to warn you, this is really more of a regular expression question than a
cmake question but since the problem is in a cmake script I thought you guys
may cut me some slack. J In any case, I have a situation where my
21 matches
Mail list logo