2013/4/4 Jean-Christophe Fillion-Robin
> Consider looking at the implementation of PreventInSourceBuilds.cmake in
> ITK
> See
> https://github.com/Kitware/ITK/blob/master/CMake/PreventInSourceBuilds.cmake
>
> May it could be generalized and integrated in CMake itself ?
>
Yes it could but it is n
Consider looking at the implementation of PreventInSourceBuilds.cmake in ITK
See
https://github.com/Kitware/ITK/blob/master/CMake/PreventInSourceBuilds.cmake
May it could be generalized and integrated in CMake itself ?
Jc
On Thu, Apr 4, 2013 at 12:49 PM, Andreas Stahl
wrote:
>
> Am 04.04.2013
Am 04.04.2013 um 17:31 schrieb Brian Milco:
>
> On Thu, Apr 4, 2013 at 6:01 AM, Daniele E. Domenichelli
> wrote:
> One benefit is that it would allow to easily remove all cmake files when
> you wrongly run cmake in the source directory instead of in the build one.
>
>
> A while ago I found
On 4 April 2013 17:32, Matthew Woehlke wrote:
>
> cd ..
> rm -rf build
> mkdir build
> cd build
>
> ...? ;-)
>
> (If your build directories tend to be in the same place, you could easily
> write a shell function to do this, to save typing.)
Done.
I should have thought of that.
Cheers,
Daniel.
-
On 2013-04-04 06:30, Daniel Carrera wrote:
On 4 April 2013 11:40, Ansis Māliņš wrote:
What would be the benefit of such a command besides syntax?
Only a small convenience, nothing big. I am used to typing "make
cleann" when I want to make sure that I am starting from a clean
slate. I also have
On 2013-04-04 11:01, Daniel Carrera wrote:
On 4 April 2013 12:41, Eric Noulard wrote:
Yes I know.
By suicidal I mean that the built tool will remove its own file
(but not the CMakeLists.txt off course).
I see what you mean. The Makefile is killing itself. It is committing suicide.
Would it be
On Thu, Apr 4, 2013 at 6:01 AM, Daniele E. Domenichelli <
daniele.domeniche...@gmail.com> wrote:
>
> One benefit is that it would allow to easily remove all cmake files when
> you wrongly run cmake in the source directory instead of in the build one.
>
>
A while ago I found the attached macro onlin
On 4 April 2013 12:41, Eric Noulard wrote:
> Yes I know.
> By suicidal I mean that the built tool will remove its own file
> (but not the CMakeLists.txt off course).
I see what you mean. The Makefile is killing itself. It is committing suicide.
Would it be a reasonable idea to delete CMakeCache.
On 04/04/13 15:34, Eric Noulard wrote:
> CMake cannot currently do that and it does not seem wise
> to ask for that feature.
> You may search the mailing list for this discussion topic and you'll find
> many answers.
>
> The only [reasonable] option is to do out-of-source build,
> then you know fo
2013/4/4 Daniele E. Domenichelli
> Hello,
>
> On 04/04/13 11:40, Ansis Māliņš wrote:
> >> Is it possible to ask CMake to make another "make clean" target
> >> that clears *all* the CMake generated files including the cache? I
> >> am a bit annoyed that the only way to clear everything is to
> >>
Hello,
On 04/04/13 11:40, Ansis Māliņš wrote:
>> Is it possible to ask CMake to make another "make clean" target
>> that clears *all* the CMake generated files including the cache? I
>> am a bit annoyed that the only way to clear everything is to
>> basically run "rm -rf *".
>
> What would be the
2013/4/4 Daniel Carrera
> On 4 April 2013 11:41, Eric Noulard wrote:
> > You can perfectly add a custom target/command to do that,
> > if you do out-of-source build then removing the build dir is ok.
>
> Thanks. Yes, I am doing out of source builds.
>
> > Now, this would be a one-shot suicidal t
On 4 April 2013 11:41, Eric Noulard wrote:
> You can perfectly add a custom target/command to do that,
> if you do out-of-source build then removing the build dir is ok.
Thanks. Yes, I am doing out of source builds.
> Now, this would be a one-shot suicidal target since this will
> basically eras
On 4 April 2013 11:40, Ansis Māliņš wrote:
> What would be the benefit of such a command besides syntax?
Only a small convenience, nothing big. I am used to typing "make
cleann" when I want to make sure that I am starting from a clean
slate. I also have my shell configured so that it warns me whe
2013/4/4 Daniel Carrera
> Hi all,
>
> Is it possible to ask CMake to make another "make clean" target that
> clears *all* the CMake generated files including the cache? I am a bit
> annoyed that the only way to clear everything is to basically run "rm
> -rf *".
>
You can perfectly add a custom t
What would be the benefit of such a command besides syntax?
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this lin
Hi all,
Is it possible to ask CMake to make another "make clean" target that
clears *all* the CMake generated files including the cache? I am a bit
annoyed that the only way to clear everything is to basically run "rm
-rf *".
Cheers,
Daniel.
--
Lord of the rings calendar in your Linux/Unix/Mac te
17 matches
Mail list logo
