| Whats the state of CMake Build Support ? [message #1764479] |
Tue, 30 May 2017 08:32  |
Eclipse User |
|
|
|
Hello,
since there is a clear lack of any information or documentation about the plugin, the only thing visible is a button to start the CMake GUI. Is this really everything it does now?
I would like to know how the following should work:
- "Seeding" configuration by storing the cmake Variables in a project. This will allow deleting the output folder, and simply starting a new build instead of configuring cmake outside of eclipse. (Like every other builder works)
- Fetching include paths and macros from the toolchain. Its not possible to enable a "Built-in Compiler settings provider", since the entire C/C++ General tree is removed from the properties
- Fetching include paths and macros from the buildsystem (what is defined per file in CMakeLists.txt)
Especially since their apparently arent any providers, the current state of the plugin is actually inferior to using a plain Makefile Project with fitting providers and running CMake yourself.
|
|
|
|
|
|
|
| Re: Whats the state of CMake Build Support ? [message #1790180 is a reply to message #1764479] |
Wed, 06 June 2018 10:19  |
| Eclipse User |
|
|
|
Hi everyone,
Executive summary:
- Intense plea for documentation.
- What and where is cmake-gui?
- How do I get Eclipse to know about Debug and Release configurations?
I've been programming Unix for decades and I finally decided to try an IDE. Eclipse seemed like the right one. In many ways I am amazed at its awesomeness!
I'm starting with a small project that builds with CMake and Ninja. I've spent days trying to figure out a good way to use Eclipse with a CMake project.
It took me over a day to figure out that "cmake4eclipse" and "CMake for CDT" are the same thing, but the new CMake support described in this email is something else. This new CMake support seems to me to be the most promising: it's under active development and it would have Eclipse builds invoking CMake and Ninja rather than Makefiles.
I don't know if it's my poor web searching skills, but I can't find ANY information on how to use this new feature. In Eclipse bug 174176, Doug Shafer writes "I'm going to mark this done. It is quite usable in it's current state." I beg to differ, a feature is not usable if other people don't have the information necessary to use it. (Apologies if I'm just being dense as to how to find it.)
The best information I found so far is in Eclipse bug 532419, in which Martin Oberhuber writes down the steps he took. Until I found that, I had no idea if I was doing the right thing. (I was.)
I am running Eclipse Oxygen.3a (4.7.3a) on Ubuntu 16.04.4. I did File->New->C++ Project and "Empty or Existing CMake Project". Somehow Eclipse figured out two things and I don't know where the information came from:
- I create a 'build' subdirectory, go there, and give the cmake command with '..' to pick up the CMakeLists.txt file.
- I use -G Ninja to tell CMake to generate Ninja files.
From Eclipse, I can click on the "build all" button and it runs CMake the way I want (if necessary) and then runs Ninja. This is great as far as it goes.
However Eclipse does not know about the standard Debug and Release configurations that CMake provides. I can't select a configuration and I can't create one.
The Project Properties->CMake panel contains nothing but a "Launch CMake GUI" button. Pressing it yields a pop-up stating that cmake-gui cannot be found.
Is the CMake GUI the same as ccmake? I hope not, since ccmake is less convenient than opening CMakeCache.txt in a text editor. Is the CMake GUI the tool that lets me inform Eclipse about my build configurations? If not, then what is?
Thank you for taking the time to read this.
Steve
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.08545 seconds
Home