Hello,
is there a possibility to generate those filters (a.k.a.
subdirectories in .vcproj files) using CMake? I managed to generate
several CMakeLists.txt files. One resides in the root directory, the
other ones in subdirectories. They are included like this:
Hi guys,
by now I was working with 2.6.2 and used a script to run multiple
builds/tests sequentially with the following structure:
snip
...
# run for the first time
SET(CTEST_SOURCE_DIRECTORY ${SOURCEROOTABS})
SET(CTEST_BINARY_DIRECTORY
2009/3/3 Michael Schantin mich...@schantin.net:
Hello,
is there a possibility to generate those filters (a.k.a.
subdirectories in .vcproj files) using CMake? I managed to generate
several CMakeLists.txt files. One resides in the root directory, the
other ones in subdirectories. They are
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
Hello,
great. This is working like a charm. I am now using
ADD_SUBDIRECTORY(mySubDir1)
ADD_SUBDIRECTORY(mySubDir2)
SOURCE_GROUP(Source Files\\mySubDir1 FILES myFirstFileInFirstDir.cpp
mySecondFileInFirstDir.cpp)
SOURCE_GROUP(Source Files\\mySubDir2 FILES
myFirstFileInSecondDir.cpp
Hi there,
Why is the firefox logo redistributed within cmake:
http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/CPack.background.png.in?root=CMakeview=log
I thought there were license restricitions when redistributing it...
Ref:
http://www.mozilla.org/foundation/trademarks/policy.html
Mathieu Malaterre wrote:
Hi there,
Why is the firefox logo redistributed within cmake:
No idea!
That file does not seem to be referenced by the build or any of the
tests, so I have removed it.
$ cvs commit -m ENH: remove unused file CPack.background.png.in
Committer: Bill Hoffman
On Mar 3, 2009, at 5:26 AM, Eric Noulard wrote:
2009/3/3 Michael Schantin mich...@schantin.net:
Hello,
is there a possibility to generate those filters (a.k.a.
subdirectories in .vcproj files) using CMake? I managed to generate
several CMakeLists.txt files. One resides in the root
2009/3/3 Michael Jackson mike.jack...@bluequartz.net:
On Mar 3, 2009, at 5:26 AM, Eric Noulard wrote:
2009/3/3 Michael Schantin mich...@schantin.net:
INCLUDE(${PROJECT_SOURCE_DIR}/mySubDir1/CMakeLists.txt)
INCLUDE(${PROJECT_SOURCE_DIR}/mySubDir2/CMakeLists.txt)
You usually don't
On Mar 3, 2009, at 8:56 AM, Eric Noulard wrote:
2009/3/3 Michael Jackson mike.jack...@bluequartz.net:
On Mar 3, 2009, at 5:26 AM, Eric Noulard wrote:
2009/3/3 Michael Schantin mich...@schantin.net:
INCLUDE(${PROJECT_SOURCE_DIR}/mySubDir1/CMakeLists.txt)
Hello all,
I'm very new to cmake, so excuse me if I'm missing some obvious
functionality that cmake already has.
I am building a project using a QNX cross-compile toolchain that I
setup. For those not familiar with the QNX toolchain, the QNX compiler
qcc is a wrapper around gcc that's mostly the
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
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
You're not missing anything per se. If you set environment variables
in your CMakeLists.txt file for some operations it's just too late. In
particular, it doesn't add commands to the build files it generates to
set the environment variables the way you need them.
You can get around this -- I
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
Thanks very much for all the hints - I appreciate it.
-Original Message-
From: cmake-boun...@cmake.org
[mailto:cmake-boun...@cmake.org] On Behalf Of Eric Noulard
2009/3/1 Alexander Neundorf a.neundorf-w...@gmx.net:
On Friday 27 February 2009, Steve Huston wrote:
Thanks for the
All,
What is the correct syntax to add a module directory to the default
module path?
I am trying to append my module directory to the default module path
using this:
SET(MY_MODULE_DIR /home/jvines/Devel/CMAKE_MODULES)
SET(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} ${MY_MODULE_DIR})
Thanks for the quick reply,
The main reason why setting the environment variables by hand is not a
clean solution is that setting environment variables globally on windows
machines requires administrator privileges. I'm sure I could get the
environment variables set on all our build machines, but
Unfortunately this isn't working either:
1 SET(MY_MODULE_DIR /home/jvines/Devel/CMAKE_MODULES)
2 LIST(APPEND CMAKE_MODULE_PATH ${MY_MODULE_DIR})
3
4 message(${CMAKE_MODULE_PATH})
I am able to find my local cmake modules but cannot find the system
cmake modules, in the cmake
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,
John,
In today's CVS HEAD of VTK, on line 51/52 of CMakeLists.txt we use these two
lines:
SET(VTK_CMAKE_DIR ${VTK_SOURCE_DIR}/CMake)
SET(CMAKE_MODULE_PATH ${VTK_CMAKE_DIR} ${CMAKE_MODULE_PATH})
to set a custom CMake module path for VTK builds. I do not know of anybody
having problems with VTK
Just use build project command on it (through right click, for example).
On 3/3/09, Anders Backman ande...@cs.umu.se wrote:
Hi all.
A slightly off-topic, but perhaps not question ;-)
Is there a way to build the INSTALL project from the command line?
Im trying the following:
devenv
As a new member of the list, I just wanted to say thanks for providing this
forum as a place to get answers about cmake!
First, the problem: I have a software system composed of a number of
source files in C. These files have an alternate file extension .bc. In
order to compile these files,
I would, if could. Thats the point.
The question was: from the command line
Not inside the IDE.
On Tue, Mar 3, 2009 at 7:29 PM, Timenkov Yuri ytimen...@gmail.com wrote:
Just use build project command on it (through right click, for example).
On 3/3/09, Anders Backman ande...@cs.umu.se
This worked for me inside the folder containing the sln file and
running from a Visual Studio 2005 command prompt.
X:\VC.80\Lung\QtBasicUtilsdevenv QtBasicUtils.sln /build Debug /project INSTALL
Microsoft (R) Visual Studio Version 8.0.50727.762.
Copyright (C) Microsoft Corp 1984-2005. All
A Dimarts 03 Març 2009, Philip Lowman va escriure:
On Mon, Mar 2, 2009 at 7:37 AM, Leopold Palomo Avellaneda
l...@alaxarxa.netwrote:
Hi,
I have a problem with one project. There's one file that doesn't accept a
some
compiler flags because g++ then has problems (templates, etc).
Hi,
I've got the following directory structure on Windows:
project/source/foo
project/bar/stuff
In the first directory, I have a CMakeLists.txt which defines a macro.
However, I am able to call that from the CMakeLists.txt inside of the second
directory. Does the scope of a macro not respect
Hi,
After reading the CMake 2.6 documentation, I'm not really clear on the
differences between a macro and a function. Could someone explain this in a
bit more detail? Based on the differences, which should I use?
___
Powered by www.kitware.com
Visit
I will assume you are doing something like this:
include(/path/to/file/with/macros.cmake)
mymacro(args)
The easiest way to think of include is the same as a C/C++ #include.
CMake will take the contents of the file and place it inline in the
cmake file that is using the 'include' command. In
The subtle difference is this line from the macro help section:
Note that the parameters to a macro and values such as ARGN are not
variables in the usual CMake sense. They are string replacements much
like the c preprocessor would do with a macro. If you want true CMake
variables you
I'm not doing that at all. Apologies for lack of detail.
For example, I will have the following:
foo/bar/CMakeLists.txt
This file has the macro definition in it.
Now in:
foo/baz/something/CMakeLists.txt
I'm able to call the macro defined in the first CMakeLists.txt file. The
only connection
Michael Jackson wrote:
The subtle difference is this line from the macro help section:
Note that the parameters to a macro and values such as ARGN are not
variables in the usual CMake sense. They are string replacements much
like the c preprocessor would do with a macro. If you want true
Hi,
I noticed after switching to version 2.6.3 that header files (with HPP
extension) are marked as Exclude from build in Visual Studio 2008. Is this
behavior by design? If so, why?
___
Powered by www.kitware.com
Visit other Kitware open-source
I suspect a typo or directory permissions issue.
Try this. Copy FindBoost.cmake from CMAKE_ROOT/share/cmake-2.6/Modules to
/home/jvines/FindBoostHOORAY.cmake. Then add the following :
set(CMAKE_MODULE_PATH /home/jvines)
set(Boost_DEBUG ON)
find_package(BoostHOORAY)
you should see output like
On Wed, Mar 4, 2009 at 12:02 AM, Michael Wild them...@gmail.com wrote:
If you add a subdirectory, it inherits all variables and macros from the
parent directories. This is actually what one expects, otherwise you would
have to repeat the whole system detection (find_pacakge, find_library,
So, this should fix the problem:
add_subdirectory(${foo_SOURCE_DIR}/../shared/lib/boost boost_lib)
Thanks, it has worked indeed, however now I'm experiencing the
following problem, running make Experimental yields this:
kurluka ~/foo/build$ make Experimental
On 4. Mar, 2009, at 7:11, Robert Dailey wrote:
On Wed, Mar 4, 2009 at 12:02 AM, Michael Wild them...@gmail.com
wrote:
If you add a subdirectory, it inherits all variables and macros
from the
parent directories. This is actually what one expects, otherwise
you would
have to repeat the
37 matches
Mail list logo
