On 3/25/2015 7:37 AM, Vaishakh wrote:
git clean -d -f -x
Build out of source.
rm -rf
-Bill
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
--
Powered by
git clean -d -f -x
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support:
Von: Ákos Maróy
Philip Lowman wrote:
I've filed a feature request for this (i.e. a distclean target for
CMake). It keeps coming up on the mailing list so it probably would
make a nice addition to CMake. I've needed it before too when stubborn
coworkers really want to keep using
Christian Ehrlicher wrote:
http://www.cmake.org/Wiki/CMake_FAQ#CMake_does_not_generate_a_.22make_distclean.22_target._Why.3F
So I doubt such a target could be added without someone crying why his
generated file did not get cleaned up...
but, you could easily create a 'best-effort' distclean,
On Tue, Mar 25, 2008 at 3:08 AM, Ákos Maróy [EMAIL PROTECTED] wrote:
Christian Ehrlicher wrote:
http://www.cmake.org/Wiki/CMake_FAQ#CMake_does_not_generate_a_.22make_distclean.22_target._Why.3F
So I doubt such a target could be added without someone crying why his
generated file did not
Philip Lowman wrote:
Yes, I agree. I'm sure there are people out there that use custom
scripts with CMake that generate files that can't be tracked by CMake.
I would argue this is a small use case. Those users shouldn't expect
CMake to clean up their stuff for them automatically. That's
There is an easy way to avoid the problem - build in a separate directory.
Separating sources is a very good practice.
Anka
Philip Lowman wrote:
On Mon, Mar 24, 2008 at 4:51 AM, Ákos Maróy [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi,
I wonder if there's an easy,
Ákos Maróy wrote:
Philip Lowman wrote:
Yes, I agree. I'm sure there are people out there that use custom
scripts with CMake that generate files that can't be tracked by
CMake. I would argue this is a small use case. Those users shouldn't
expect CMake to clean up their stuff for them
Hi,
I wonder if there's an easy, straightforward way to clean a cmake
project of _all_ cmake-generated files? This would include:
CMakeCache.txt
cmake_install.cmake
CMakeFiles
and all of these in subdirectories added to the project with the
add_subdirectory() statement..
Thanks,
Akos
On Monday 24 March 2008 12:23:04 Ákos Maróy wrote:
Andreas Pakulat wrote:
Use out-of-source builds, then you can just rm -rf builddir and be done.
I'd love to, but I want to use Eclipse for the building itself, and it
seems Eclipse needs in-source builds to be able to do meaningful
On Mon, Mar 24, 2008 at 4:51 AM, Ákos Maróy [EMAIL PROTECTED] wrote:
Hi,
I wonder if there's an easy, straightforward way to clean a cmake
project of _all_ cmake-generated files? This would include:
CMakeCache.txt
cmake_install.cmake
CMakeFiles
and all of these in subdirectories added
11 matches
Mail list logo