|
|
| (66 intermediate revisions by 13 users not shown) |
| Line 1: |
Line 1: |
| == Obtaining Eclipse + CDT ==
| | {{CMake/Template/Moved}} |
| [http://www.eclipse.org Eclipse IDE] is an IDE written in Java that was initially use for developing java programs. In the years lots of projects have used eclipse as a base for their own applications. One such project is the "C/C++ Development Tools" or CDT. The home page is. [http://www.eclipse.org/cdt/ here]
| |
|
| |
|
| You can download a CDT Version of Eclipse that does NOT include all the other Java Development tools [http://www.eclipse.org/downloads/ here]. Just select the "Eclipse IDE for C/C++ Developers" link on that page.
| | This page has moved [https://gitlab.kitware.com/cmake/community/wikis/doc/editors/Eclipse-UNIX-Tutorial here]. |
| | |
| == CMake Editor Plugin for Eclipse ==
| |
| There is also an editor plug-in for Eclipse available (see above): [http://www.cthing.com/CMakeEd.asp CMake Editor].
| |
| | |
| == Eclipse + CDT Version Information ==
| |
| CDT 3.1.2 goes with Eclipse 3.2 <br>
| |
| CDT 4.0 goes with Eclipse 3.3.
| |
| | |
| I highly recommend CDT 4.0 as the feature set is vastly improved, most notably the indexer which has become super fast. The syntax highlighting improvements are also very nice. There are now at least 3 C/C++ code formatters available (or edit/create your own style rules). Numerous other improvements are also incorporated into the release. Eclipse 3.3 does require Java 1.5 (5.0) jvm.
| |
| | |
| == File System Setup ==
| |
| Eclipse CDT supports projects that already provide a makefile so this is good news for CMake users.
| |
| | |
| The basic steps to get Eclipse + CDT + CMake working are:
| |
| 1) Use CMake to generate makefiles for your project
| |
| 2) Create a new project in Eclipse using the top level directory of your project as the "Project Directory". The type of project to create should be a "Makefile C++"
| |
| 3) Create an "External Tool" to run cmake from within Eclipse
| |
| | |
| Eclipse CDT can interoperate with CMake by creating a "Standard Makefile" project, running CMake, and then having CDT to run make on the generated makefiles. Eclipse CDT works better if the build files are somewhere in project directory such as a subdirectory (for example Build).
| |
| | |
| A typical workflow would be something like this.
| |
| | |
| In a terminal program "cd" into the top level of your project directory ideally where your CMakeLists.txt file resides. Create a directory called "Build".
| |
| cd into Build and then run ccmake/cmake using the parent directory as the target for cmake. So, for example if we have a project called "MyGreatProject" located in /Users/mike/Projects, then the terminal commands would look like the following:
| |
| | |
| [mjackson@Thor:]$ cd /Users/mike/Workspace/MyProject
| |
| [mjackson@Thor:]$ mkdir Build
| |
| [mjackson@Thor:]$ cd Build
| |
| [mjackson@Thor:]$ ccmake ../
| |
|
| |
| [[Image:Eclipse Tutorial 1.png|Basic Project Setup]]<br>
| |
| '''Image showing the basic Project setup for our tutorial.'''
| |
| | |
| At this point we have bootstrapped the process somewhat so Eclipse throws less errors when we setup the Eclipse Projects.
| |
| | |
| == Eclipse Project Setup ==
| |
| | |
| '''Launch Eclipse and go to "New->C++ Project" Menu'''
| |
| [[Image:Eclipse_NewProjectMenu.png|New Project Menu]]
| |
| | |
| <br>
| |
| '''Select the MakeFile Project type'''
| |
| [[Image:Eclipse_wizard_1.png|Project Wizard Makefile Selection]]
| |
| | |
| <br>
| |
| '''Select the ''Advanced Settings'' Button'''
| |
| [[Image:Eclipse_wizard_2.png|Project Wizard Setting Project Type]]
| |
| | |
| <br>
| |
| '''Uncheck the ''Use Default Build Command'''''
| |
| '''Insert the following in the ''Build Command'' Text Field: ''make -C ${project_loc}/Build'''''
| |
| [[Image:Eclipse_wizard_3.png|Project Wizard Advanced Options]]
| |
| | |
| <br>
| |
| <b>Disclose the "C/C++ Build" options, and select "Settings". In the Right Side pane select the binary format for your system.</b>
| |
| <b>Click on the OK Button. Your project is now ready.</b>
| |
| [[Image:Eclipse_wizard_4.png|Project Wizard Setting binary Parser]]
| |
| | |
| | |
| {| border="1"
| |
| |- bgcolor="#abcdef"
| |
| ! Our Finished Project showing off <br/>some of the C++ semantic highlighting capabilities !! Eclipse showing the CMakeEditor Plugin
| |
| |-
| |
| | [[Image:Eclipse_project_finished.png|thumb|Project Wizard]] || [[Image:Eclipse_Cmake_Editor.png|thumb|CMakeEditor Screen Shot]]
| |
| |}
| |
| | |
| == Creating an External Tool to run cmake ==
| |
|
| |
| If you edit your CMakeLists.txt file, then you will need to go back out to your terminal and rerun cmake. OR you can create an external program launch configuration and run cmake from within eclipse. To do this select the "Run->External Tools->Show External Tools Dialog..." menu.
| |
| Create a new "Program" and call it Cmake. in the "Location" text field, type the absolute path to cmake (/usr/local/bin/cmake). If the "Working Directory" area insert the following: "${project_loc}/Build" and in the Arguments section insert the following: "../". In the "Refresh Tab" Select ""The project containing the selected resources". In the "Common" tab check the "External Tools" selection. This will put a shortcut in the "Run" menu for you. Click the Apply Button and then run. cmake will now run on your project directory.
| |
| | |
| == Parsing Errors more efficiently ==
| |
| | |
| The CDT Error Parser cannot handle error messages that span more than one line, which is the default gcc behavior. In order to
| |
| force gcc to generate single line error messages with no line wrapping, add to your CMakeLists.txt:
| |
| | |
| IF(CMAKE_COMPILER_IS_GNUCC)
| |
| SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -fmessage-length=0")
| |
| ENDIF(CMAKE_COMPILER_IS_GNUCC)
| |
| IF(CMAKE_COMPILER_IS_GNUCXX)
| |
| SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fmessage-length=0")
| |
| ENDIF(CMAKE_COMPILER_IS_GNUCXX)
| |
| | |
| == Automatic Discovery of Include directories and other compiler items ==
| |
| In order for the CDT discovery mechanism to catch the compiler options and definitions automatically from the
| |
| build output, enable the "Enable build output info discovery" in the project properties and set the CMAKE_VERBOSE_MAKEFILE
| |
| variable in your CMakeLists.txt.
| |
| | |
| SET(CMAKE_VERBOSE_MAKEFILE ON)
| |
| | |
| If you don't want to hard-code this behavior in CMakeLists.txt, you can achieve the same effect by
| |
| telling CDT to invoke make as
| |
| | |
| make -C ${project_loc}/Build VERBOSE=1
| |
| | |
| == Multiple Make Jobs for Multi-Core Hardware ==
| |
| If you have a multi-core hardware system (Intel Core Duo or the like) you can use the following to invoke more than one compile job:
| |
| | |
| make -C ${project_loc}/Build -j2
| |
| | |
| Where '2' is the number of jobs to have make run.
| |
| | |
| == True Out of Source Builds ==
| |
| You can <i>still</i> do out of source builds if you want. The make command would be the following if you have created your build directory at the same level as your project directory and called it "MyProjectBuild"
| |
| | |
| make -C ${project_loc}/../MyProjectBuild
| |
| | |
| While this will work, what you will be missing is the list of binaries in your project view which makes setup of Debugging and Running your executable easier. All this can <i>still</i> be setup through custom run and debug commands in eclipse. I will leave that as an exercise to the reader.
| |
