Am Freitag, 5. April 2019, 00:07:08 CEST schrieb Benjamin Shadwick:
> Ah, it seems my CMake is too old to produce compile_commands.json. Maybe
> this is part of why other IDEs are working better at home on Ubuntu MATE
> LTS.
>
> Unfortunately Red Hat ships CMake 2.8.12.2 even in recent RHEL releas
Ah, it seems my CMake is too old to produce compile_commands.json. Maybe
this is part of why other IDEs are working better at home on Ubuntu MATE
LTS.
Unfortunately Red Hat ships CMake 2.8.12.2 even in recent RHEL releases,
which is now approaching 5 years old (yikes!). Apparently they ship CMake
On Wed, Apr 3, 2019 at 2:50 PM Martin Weber
wrote:
> To implement the 'index only files referenced through the build script'
> view,
> *any* IDE would have to *interpret* the build scripts.
> Just choose an IDE that has a build script interpreter to solve your use
> case.
>
Qt Creator and Visual
Am Mittwoch, 3. April 2019, 22:55:45 CEST schrieb Benjamin Shadwick:
> FYI,
>
> I opened a bug on CMake's tracker about updating the CMake generator since
> its outputs are kind of garbage for modern CDT releases:
> https://gitlab.kitware.com/cmake/cmake/issues/19107
>
> Unfortunately the only fe
Am Mittwoch, 3. April 2019, 22:26:59 CEST schrieb Benjamin Shadwick:
> I tried cmake4eclipse, and it's a mixed bag. It requires a lot of tweaking
Really? Just set _CMake Builder (portable)_ as the current builder and build.
> of the Eclipse project after you create it, and I'm pretty sure it suff
FYI,
I opened a bug on CMake's tracker about updating the CMake generator since
its outputs are kind of garbage for modern CDT releases:
https://gitlab.kitware.com/cmake/cmake/issues/19107
Unfortunately the only feedback I got was that there is a push to remove
*all* generators in favor of forcin
Am Mittwoch, 3. April 2019, 18:44:04 CEST schrieb Benjamin Shadwick:
> Update - I think I found a tolerable workaround:
>
> If I invoke cmake with -DCMAKE_ECLIPSE_GENERATE_LINKED_RESOURCES=OFF and
> then inject a link to my include directory into the .project file, things
> work a lot better:
You
I tried cmake4eclipse, and it's a mixed bag. It requires a lot of tweaking
of the Eclipse project after you create it, and I'm pretty sure it suffers
from the same problem of leaving you with an Eclipse project whose source
tree reflects what is in the filesystem rather than what is defined in the
Am Mittwoch, 3. April 2019, 18:44:04 CEST schrieb Benjamin Shadwick:
> Update - I think I found a tolerable workaround:
>
> If I invoke cmake with -DCMAKE_ECLIPSE_GENERATE_LINKED_RESOURCES=OFF and
> then inject a link to my include directory into the .project file, things
> work a lot better:
> -
Update - I think I found a tolerable workaround:
If I invoke cmake with -DCMAKE_ECLIPSE_GENERATE_LINKED_RESOURCES=OFF and
then inject a link to my include directory into the .project file, things
work a lot better:
- I get only one copy of each source file in the Open Resource dialog.
- I get sour
I've recently converted a complex C++ codebase to CMake. I'm stuck using
2.8.12.2.
The codebase has a source tree, whose leaf directories each build a shared
library or an executable binary. The source lives in src/ while the headers
live in a separate tree under a sibling include/ directory.
Bas
11 matches
Mail list logo