On Sunday 10 October 2010 14:56:29 Alexander Neundorf wrote:
On Friday 08 October 2010, David Cole wrote:
On Fri, Oct 8, 2010 at 10:59 AM, Alexander Neundorf
neund...@kde.orgwrote:
...
Better idea:
I'll add a policy which switches this behaviour (prefer CMAKE_ROOT over
On 10/11/2010 02:54 PM, Brad King wrote:
I just tested it with the COnly test and VS9 x64. It now reloads even
when the project has not changed at all (touch CMakeLists.txt). I
wonder if the project solution folder feature affected this.
It happens when the USE_FOLDERS property is on. The
On Mon, Oct 11, 2010 at 2:37 PM, Brad King brad.k...@kitware.com wrote:
On 10/11/2010 02:54 PM, Brad King wrote:
I just tested it with the COnly test and VS9 x64. It now reloads even
when the project has not changed at all (touch CMakeLists.txt). I
wonder if the project solution folder
On Monday 11 October 2010, Marcus D. Hanwell wrote:
On Sunday 10 October 2010 14:56:29 Alexander Neundorf wrote:
...
So is there no chance of fixing this in a backward compatible way? One of
Prefering module in CMAKE_ROOT when include() or find_package() is called from
CMAKE_ROOT (which does
On Mon, Oct 11, 2010 at 5:00 PM, Alexander Neundorf neund...@kde.orgwrote:
On Monday 11 October 2010, Marcus D. Hanwell wrote:
On Sunday 10 October 2010 14:56:29 Alexander Neundorf wrote:
...
So is there no chance of fixing this in a backward compatible way? One of
Prefering module in
On 11. Oct, 2010, at 24:13 , Andreas Pakulat wrote:
On 10.10.10 21:41:05, Jochen Wilhelmy wrote:
Hi!
Is it possible to define the current working directory of a command line
tool
that is built with cmake? since the build is usually out-of-source I have
to set the current working
Hello, everybody!
I've just tried to compile regular expression matches any string, ends with
set of symbols, including right square bracket. How can I do that?
If I specify .*[\]})] cmake prints error:
Syntax error in cmake code at /home/dimm/test/test.cmake:3 when parsing string
.*[\]})]
Hi!
Is it possible to define the current working directory of a command line
tool
that is built with cmake? since the build is usually out-of-source I have
to set the current working directory in the ide, e.g visual studio or
xcode. more convenient would be to set it in cmake.
Do you
On 11.10.10 10:07:58, Jochen Wilhelmy wrote:
Hi!
Is it possible to define the current working directory of a command line
tool
that is built with cmake? since the build is usually out-of-source I have
to set the current working directory in the ide, e.g visual studio or
xcode. more
On 11. Oct, 2010, at 10:07 , Jochen Wilhelmy wrote:
Hi!
Is it possible to define the current working directory of a command line
tool
that is built with cmake? since the build is usually out-of-source I have
to set the current working directory in the ide, e.g visual studio or
xcode. more
Hi!
Is it possible to define the current working directory of a command line
tool
that is built with cmake? since the build is usually out-of-source I have
to set the current working directory in the ide, e.g visual studio or
xcode. more convenient would be to set it in cmake.
On 11. Oct, 2010, at 11:20 , Jochen Wilhelmy wrote:
Hi!
Is it possible to define the current working directory of a command line
tool
that is built with cmake? since the build is usually out-of-source I
have
to set the current working directory in the ide, e.g visual studio or
Hello,
I suppose this question has already been asked here but I did not find any
trace of it, including in the wiki.
My students want to install PV at home and they need to build it from source in
order to extend it.
They do have a version installed at the university and, since configuring and
On Mon, Oct 11, 2010 at 9:32 AM, Fred Fred stan1...@hotmail.fr wrote:
Hello,
I suppose this question has already been asked here but I did not find any
trace of it, including in the wiki.
My students want to install PV at home and they need to build it from source
in order to extend it.
They
So it is impossible to just extract the options from the environment config
data.
But you suggestion is fine although it requires some work lol
Thx
Date: Mon, 11 Oct 2010 09:42:24 -0400
Subject: Re: [CMake] Reusing configuration
From: dresche...@gmail.com
To: stan1...@hotmail.fr
CC:
On 11. Oct, 2010, at 15:47 , Fred Fred wrote:
So it is impossible to just extract the options from the environment config
data.
But you suggestion is fine although it requires some work lol
Thx
Date: Mon, 11 Oct 2010 09:42:24 -0400
Subject: Re: [CMake] Reusing configuration
From:
Well, the line with the set(ParaView_DIR ...) should be before the
FIND_PACKAGE call, although one usually sets this variable only in the cache if
CMake isn't able ParaView on its own.
Michael
On 11. Oct, 2010, at 16:54 , Fred Fred wrote:
Yes, actually I did not remember that install
Actually I did already make the test, ie putting this line on top, but it does
not change anything.
Subject: Re: [CMake] Reusing configuration
From: them...@gmail.com
Date: Mon, 11 Oct 2010 17:04:22 +0200
CC: cmake@cmake.org
To: stan1...@hotmail.fr
Well, the line with the
Ahh, sorry. I didn't look at the error closely. Try this:
$ export
LD_LIBRARY_PATH=/ParaView-Development-3.8.1-Linux-i686/lib/paraview-3.8:$LD_LIBRARY_PATH
$ make
Michael
On 11. Oct, 2010, at 17:09 , Fred Fred wrote:
Actually I did already make the test, ie putting this line on top, but it
On 10/9/2010 8:25 AM, Dimitri Kaparis wrote:
Greetings,
Using CMake 2.8.2. The Visual C++ 2008 generator applies preprocessor
definitions to the resource files in the project (the preprocessor
definitions property in the Resources section of the project
contains , e.g. the macros added with
Of course, I did it actually but I hoped that the cmake configuration could
handle it by itself.
Anyway, let us go to a more complicated issue: my plugin uses VTK variable and
thus requires including vtk header files. I suppose that any serious plugin
code would do it.
The problem is I get a
On 10/11/2010 11:20 AM, Jochen Wilhelmy wrote:
Hi!
Is it possible to define the current working directory of a command line
tool
that is built with cmake? since the build is usually out-of-source I
have
to set the current working directory in the ide, e.g visual studio or
xcode.
You could look at my CreateLaunchers.cmake script, in
http://github.com/rpavlik/wiimote-head-tracker-gui/tree/master/cmake/ -
I use this so that I can click the run button in Visual Studio, it
produces the files needed to set that up properly. (The only caveat is
that you can't have visual
Hi,
We are working on Visual Studio 2008 COM project which has IDL files and
need MIDL to generate the .TLB and header and source files, and we faced
with 2 issues. We made changes from the attached patch and the diff to
2.8.2 cmLocalVisualStudio7Generator.cxx and finally it works.
The
Hi,
I did a quick scan looking for this but didn't see this mentioned in
the FAQ.
Is there a documented process for compiling a single source file
multiple times? For example, the UMFPACK library need to compile most
source files at least twice with a different set of defined macros for
On Mon, Oct 11, 2010 at 2:20 AM, Jochen Wilhelmy j.wilhe...@arcor.de wrote:
Hi!
Is it possible to define the current working directory of a command
line
tool
that is built with cmake? since the build is usually out-of-source I
have
to set the current working directory in the ide, e.g
On 10/11/2010 10:04 PM, Belcourt, Kenneth wrote:
Hi,
I did a quick scan looking for this but didn't see this mentioned in
the FAQ.
Is there a documented process for compiling a single source file
multiple times? For example, the UMFPACK library need to compile most
source files at
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 1b440f7607531fc6d0f07d6a291f03240504ffdd (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via d6ba7de81526c2f97b041cc9e2f40267b9ea0cc2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 94040d6299c4afc8bc5244ee8905f41731459bfe (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via ad39bab508c9b61616a6bf2f58e9ef931402f850 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 3810da1a73de50da76aa014876e606819d51a945 (commit)
from
32 matches
Mail list logo
