In Eclipse Photon there is a new option to import cmake projects directly. Since most people probably want to use Ninja for builds these days (who wants to wait 30+ secs for a warm build just to see what is dirty?), that rules out the only way of importing this information via makefiles that is currently supported, unless you want to have to generate two separate build systems every time you configure, which would make automation a real pain (given that cmake re-runs itself when the lists change).

If you have boost in your repo, or a medium or large sized tree, indexing everything simply isn't going to work in the real world - not with speed and reliability of Eclipse's indexer anyway. Otherwise we would end up indexing everything, and badly, without the correct macros being defined. Why? Simply because Eclipse must obtain the preprocessor defines, include paths, and what files are included in the build from somewhere. In short, only the CDT generator is currently a viable option. If you make any changes to your build configuration (such as editing Makefile.am), you will need to re-run the last command in order for Eclipse to pick up the changes.I used cmake for the workspace subdir, but you can use a name of your choice.

Make sure Copy projects into workspace is NOT checked.Ĭlick Finish and you have a CMake project in your workspace. > General > Existing Projects into WorkspaceĬheck Select root directory and choose ~/workspaces/someproject/cmake. Data which I need to build or test the project goes in subdirs of the project's workspace dir, so I suggest doing the same for CMake.Īssuming both your workspace and source folders are named someproject, do: cd ~/workspaces/someprojectĬmake -G 'Eclipse CDT4 - Unix Makefiles' ~/src/someprojectįile > Import.

I prefer to keep my Eclipse workspaces in ~/workspaces and the source code in ~/src. Elaborating on arrowd's answer for Eclipse:įirst, choose a directory for the CMake files.

Eclipse cdt ubuntu