Re: [CMake] Disallowing in-source builds

2010-10-09 Thread Joshua L. Blocher
This is how is it done in KDE SC. http://websvn.kde.org/trunk/KDE/kdelibs/cmake/modules/MacroEnsureOutOfSourceBuild.cmake?view=markup Joshua L. Blocher ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [CMake] Disallowing in-source builds

2010-10-08 Thread aaron.meadows
CMakeCache.txt to be loaded in the build tree when cmake is next run. Aaron C. Meadows -Original Message- From: Michael Wild [mailto:them...@gmail.com] Sent: Thursday, October 07, 2010 2:20 AM To: Meadows, Aaron C.; Meadows, Aaron C. Cc: cmake@cmake.org Subject: Re: [CMake] Disallowing

Re: [CMake] Disallowing in-source builds

2010-10-07 Thread Michael Wild
On 6. Oct, 2010, at 20:10 , aaron.mead...@thomsonreuters.com aaron.mead...@thomsonreuters.com wrote: Hi all. Is there a good way to disallow in-source builds? Ideally, I'd like to prevent it before any cruft is written into the source tree. I experimented with writing a function

[CMake] Disallowing in-source builds

2010-10-07 Thread fatman
is there an easy way to clean out a source tree if an in-source build was accidentally kicked off? (short of dividing the files by their timestamp and removing the newer ones, etc..) My immediate thought was, does make clean not work for you? But I guess you're talking about CMake debris

Re: [CMake] Disallowing in-source builds

2010-10-07 Thread Mateusz Loskot
On 07/10/10 10:21, fat...@crackmonkey.us wrote: Then, to clear all CMake debris: rm -r projectx/cmake/* On Unix, if a project is managed by SVN it's easy to clean tree from generated files: $ svn-clean Distributed with Debian, Ubuntu, etc. as well as downloadable [1] I'm sure there are

Re: [CMake] Disallowing in-source builds

2010-10-07 Thread Philip Lowman
On Thu, Oct 7, 2010 at 3:19 AM, Michael Wild them...@gmail.com wrote: On 6. Oct, 2010, at 20:10 , aaron.mead...@thomsonreuters.com aaron.mead...@thomsonreuters.com wrote: Hi all. Is there a good way to disallow in-source builds? Ideally, I'd like to prevent it before any cruft

Re: [CMake] Disallowing in-source builds

2010-10-07 Thread kent williams
Two things: You should have your source code under version control, for many reasons, but in this context: 1. The VC system can tell you which files are unknown to it, i.e. those CMake pooped all over your source tree. 2. You can make sure your work is checked in, then delete the source

Re: [CMake] Disallowing in-source builds

2010-10-07 Thread aaron.meadows
Yeah, I think I'll go with something like what you are saying. I wonder if I can remove the CMakeFiles directory and the CMakeCache.txt file from within the CMakeLists script... Aaron C. Meadows Hi all. Is there a good way to disallow in-source builds? Ideally, I'd like to prevent

Re: [CMake] Disallowing in-source builds

2010-10-07 Thread kent williams
You could try, though it makes my brain hurt to think about it. Why go to such lengths to protect users from themselves? On Thu, Oct 7, 2010 at 11:57 AM, aaron.mead...@thomsonreuters.com wrote: Yeah, I think I'll go with something like what you are saying.  I wonder if I can remove the

Re: [CMake] Disallowing in-source builds

2010-10-07 Thread aaron.meadows
take care of that shortly...) Aaron C. Meadows -Original Message- From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of kent williams Sent: Thursday, October 07, 2010 12:55 PM To: CMake ML Subject: Re: [CMake] Disallowing in-source builds You could try, though

Re: [CMake] Disallowing in-source builds

2010-10-06 Thread Philip Lowman
On Wed, Oct 6, 2010 at 2:10 PM, aaron.mead...@thomsonreuters.com wrote: *Hi all.* * * *Is there a good way to disallow in-source builds? Ideally, I’d like to prevent it before any cruft is written into the source tree. I experimented with writing a function into my CMakelists file and