[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cmake
Subject:    Re: [CMake] Why simple `cmake` does not launch default generator on current directory?
From:       Matthew Woehlke <mw_triad () users ! sourceforge ! net>
Date:       2014-06-13 17:57:08
Message-ID: lnfe1k$mr9$1 () ger ! gmane ! org
[Download RAW message or body]

On 2014-06-12 06:18, Adam Strzelecki wrote:
> > [why does 'cmake .' configure something but 'cmake' does not?]
> 
> It is clear to me that out-of-source builds are better for many reasons, but I \
> don't see how `cmake` dumping 3 pages of usage not mentioning anything about that \
> lets user to understand that. 
> Moreover there is a lack of consequence whether path argument is obligatory or not, \
> because `cmake -GNinja` or `cmake -DDUMMY=1` works in source directory without \
> needing to specify extra dot.

Um. Wow. I had to try that to believe it really works. That feels like a
bug to me :-). (It also means the usage lies; the usage implies that the
path is required, but apparently not...)

-- 
Matthew

-- 

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: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at \
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake


[prev in list] [next in list] [prev in thread] [next in thread]