Eric Noulard wrote:
Fair enough,
my tortuous mind was tracking the build tree yours
is tracking the source tree, this is obviously a
better choice.
My E3) case still remains, you really don't want to mess-up
an existing build tree with a unrelated source tree.
I know however that my
Well...I didn't foresee such a discussion on the topic but have actually
heard some interesting new things brought up...so I guess I can chime in too.
1. Being able to call cmake with
$ cmake build dir source dir
Although it is better than what we have now, I like the explicit
nature
On 2009-09-07 08:43-0400 Brad King wrote:
I know however that my proposal does not solve the other problem
regarding ignoring path-to-existing-build raised in this thread.
That use case will not be dropped. I think the two-path auto-magic
command line interpretation approach will work well
An important clarification is that any kind of PreConfigure.cmake
file would be loaded without any build tree or cache. Anything it
does won't make it into the real CMakeLists.txt processing...no
variables or cache settings. The file would be an interface to
tell CMake about some project
2009/9/7 Alan W. Irwin ir...@beluga.phys.uvic.ca:
On 2009-09-07 08:43-0400 Brad King wrote:
1.) Simply error-out and tell the user to build out-of-source.
The source tree will remain clean.
Projects can obviously do (1) already by the appropriate IF(CMAKE_BINARY_DIR
STREQUAL
Am Freitag 04 September 2009 21:58:02 schrieb Alexander Neundorf:
On Sunday 09 August 2009, Roman Shtylman wrote:
I have been meaning to try and create such a patch for a while. The
idea behind the patch is that you can specify the location of the out
of source build directory on the
On 2009-09-05 09:38+0200 Hendrik Sattler wrote:
The problem with how giving the build-dir/source-dir to cmake is currently too
much dependent on other conditions:
cmake [options] path-to-source
cmake [options] path-to-existing-build
The first only is true if no CMakeCache.txt exists there.
2009/9/5 Bill Hoffman bill.hoff...@kitware.com:
Alan W. Irwin wrote:
On 2009-09-05 09:38+0200 Hendrik Sattler wrote:
The problem with how giving the build-dir/source-dir to cmake is
currently too
much dependent on other conditions:
cmake [options] path-to-source
cmake [options]
Continued
2) In the same way I did file a bug report for being able to enforce
out-of-source if necessary.
http://public.kitware.com/Bug/view.php?id=6672
2009/9/5 Bill Hoffman bill.hoff...@kitware.com:
I use this all the time, and so do lots of people that I know. They do this:
On 2009-09-05 10:59-0400 Bill Hoffman wrote:
Alan W. Irwin wrote:
On 2009-09-05 09:38+0200 Hendrik Sattler wrote:
The problem with how giving the build-dir/source-dir to cmake is currently
too
much dependent on other conditions:
cmake [options] path-to-source
cmake [options]
Am Samstag 05 September 2009 16:59:09 schrieb Bill Hoffman:
I use this all the time, and so do lots of people that I know. They do
this:
cmake .
I also use this. But being able to force a specific build dir (instead of cmake
trying to be smart) may be a good thing, like ignoring the
On Saturday 05 September 2009, Eric Noulard wrote:
Continued
...
CMake may guess which one is the build tree using this algorithm.
1) If there is a CMakeCache.txt in the dir then this is a build tree
2) If the path does not exists then this is a to be created build tree
error cases are:
2009/9/5 Alexander Neundorf a.neundorf-w...@gmx.net:
On Saturday 05 September 2009, Eric Noulard wrote:
[...]
E3) One gives a build tree which does not correspond to the given source
tree This is easy to check because CMakeCache.txt contains
PROJECT_SOURCE_DIR
If this
I have been meaning to try and create such a patch for a while. The
idea behind the patch is that you can specify the location of the out
of source build directory on the command line. By itself, this really
isn't all that useful save having to type mkdir 'some dir', cd 'some
dir', and 'cmake ..'
14 matches
Mail list logo
