Hello,
Sorry for reviving an old thread
(https://cmake.org/pipermail/cmake/2013-December/056517.html) but it seems to
have died without a proper answer, at least one that I could find.
I'd like to offer an additional reason why CMAKE_EXPORT_COMPILE_COMMANDS would
be beneficial if on by default
On Sunday 08 December 2013, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > It sounds to me a bit more like it should be an additional "extra"
> > generator, i.e. generate makefiles/ninja files and additionally this json
> > file.
>
> Hmm, the first thing I thought when I saw your kate projec
Alexander Neundorf wrote:
> It sounds to me a bit more like it should be an additional "extra"
> generator, i.e. generate makefiles/ninja files and additionally this json
> file.
Hmm, the first thing I thought when I saw your kate project feature was that
it should be implemented more like CMAKE
On Monday 02 December 2013, Martin Zenzes wrote:
> Hi,
>
> is there a reason why the cmake-option "CMAKE_EXPORT_COMPILE_COMMANDS"
> is not enabled by default? It was exposed as an option in 2011 [1], a
> few days after adding it initially. It can be enabled manually by adding
> "set(CMAKE_EXPORT_C
Hi,
is there a reason why the cmake-option "CMAKE_EXPORT_COMPILE_COMMANDS"
is not enabled by default? It was exposed as an option in 2011 [1], a
few days after adding it initially. It can be enabled manually by adding
"set(CMAKE_EXPORT_COMPILE_COMMANDS ON)" into the CMakeLists.txt or
giving t
