Difference between revisions of "KDevelop4/Manual/Building (compiling) projects with custom Makefiles"

m (add category)
m (Mentioning Jump to Next Outputmark menu item)
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Building (compiling) projects with custom Makefiles ==
+
<languages />
 +
<translate>
  
Many projects describe how source files have to be compiled (and which files have to be recompiled once a source or header file changes) using Makefiles that are interpreted by the "make" program (see, for example, [http://www.gnu.org/software/make/ GNU make]). For simple projects, it is often very easy to set up such a file by hand. Larger projects often integrate their Makefiles with the GNU autotools (autoconf, autoheader, automake). In this section, let us simply assume that you have a Makefile for your project and you want to teach KDevelop how to interact with it.
+
== Building (compiling) projects with custom Makefiles == <!--T:1-->
  
{{Note|1=KDevelop 4.x doesn't know about the GNU autotools at the time this section is written. If your project uses them, you will have to run <code>./configure</code> or any of the other related commands by hand on a command line. If you want to do this within KDevelop, open the '''Konsole''' tool (if necessary add it to the perimeter of the main window using the menu <menuchoice>Windows > Add tool view</menuchoice>) that gives you a shell window view and run <code>./configure</code> from the command line in this view.}}
+
<!--T:2-->
 +
Many projects describe how source files have to be compiled (and which files have to be recompiled once a source or header file changes) using Makefiles that are interpreted by the '''make''' program (see, for example, [http://www.gnu.org/software/make/ GNU make]). For simple projects, it is often very easy to set up such a file by hand. Larger projects often integrate their Makefiles with the '''GNU autotools''' (autoconf, autoheader, automake). In this section, let us simply assume that you have a Makefile for your project and you want to teach '''KDevelop''' how to interact with it.
  
The first step is to teach KDevelop about targets in your Makefiles. There
+
<!--T:3-->
are two ways to do that: selecting individual Makefile targets, and choosing a
+
{{Note|1='''KDevelop''' 4.x doesn't know about the '''GNU autotools''' at the time this section is written. If your project uses them, you will have to run <code>./configure</code> or any of the other related commands by hand on a command line. If you want to do this within '''KDevelop''', open the '''Konsole''' tool (if necessary add it to the perimeter of the main window using the menu <menuchoice>Windows -> Add tool view</menuchoice>) that gives you a shell window view and run <code>./configure</code> from the command line in this view.}}
set of targets you may want to build frequently. For both approaches, open
 
the "Projects" tool by clicking on the "Projects" button on the perimeter of
 
KDevelop's main window (if you don't have this button see above how to add a
 
tool's button there). The "Projects" tool window has two parts: the top half
 
&mdash; titled "Projects" &mdash; lists all of your projects and let's you
 
expand the underlying directory trees. The bottom half &mdash; titled "Project
 
Selection" &mdash; lists a subset of those projects that will be built if you
 
choose the menu item "Project > Build selection" or hit F8; we'll come back to
 
this part below.
 
  
=== Building individual Makefile targets ===
+
<!--T:4-->
 +
The first step is to teach '''KDevelop''' about targets in your Makefiles. There are two ways to do that: selecting individual Makefile targets, and choosing a set of targets you may want to build frequently. For both approaches, open
 +
the '''Projects''' tool by clicking on the <menuchoice>Projects</menuchoice> button on the perimeter of '''KDevelop's''' main window (if you don't have this button see above how to add a tool's button there). The '''Projects''' tool window has two parts: the top half &mdash; titled '''Projects''' &mdash; lists all of your projects and let's you expand the underlying directory trees. The bottom half &mdash; titled '''Project Selection''' &mdash; lists a subset of those projects that will be built if you choose the menu item <menuchoice>Project -> Build selection</menuchoice> or hit <keycap>F8</keycap>; we'll come back to this part below.
  
In the top part of the project view, expand the sub-tree for one project,
+
</translate><span id="Building individual Makefile targets"></span><translate>
let's say the one for which you want to run a particular Makefile target. This will give you icons for (i) directories
 
under this project, (ii) files in the top-level directory for this project,
 
(iii) Makefile targets KDevelop can identify. These categories are shown in the picture at right. Note that KDevelop <i>understands</i> Makefile syntax to a certain degree and therefore can offer you targets defined in this Makefile (though this understanding has its limits if targets are composed or implicit).
 
  
[[Image:kdevelop-1a.png|thumb|500px|right]]
+
=== Building individual Makefile targets === <!--T:5-->
  
To build any of the targets listed there, click on it with the right mouse button and select "Build". For example, doing this with the "clean" target will simply execute "make clean". You can see this happening in the subwindow titled "Build" that opens up, showing the command and the output. (This window corresponds to the "Build" tool, so you can close and later re-open the window using the "Build" tool button on the perimeter of the main window. It is shown at the bottom right of the picture.)
+
<!--T:6-->
 +
In the top part of the project view, expand the sub-tree for one project, let's say the one for which you want to run a particular Makefile target. This will give you icons for (i) directories under this project, (ii) files in the top-level directory for this project, (iii) Makefile targets '''KDevelop''' can identify. These categories are shown in the picture at right. Note that '''KDevelop''' ''understands'' Makefile syntax to a certain degree and therefore can offer you targets defined in this Makefile (though this understanding has its limits if targets are composed or implicit).
  
=== Selecting a collection of Makefile targets for repeated building ===
+
<!--T:7-->
 +
[[Image:kdevelop-1a.png|thumb|500px|center]]
  
Right-clicking on individual Makefile targets every time you want to build
+
<!--T:8-->
something will quickly get old. Rather, we'd like to have individual targets
+
To build any of the targets listed there, click on it with the right mouse button and select <menuchoice>Build</menuchoice>. For example, doing this with the "clean" target will simply execute "make clean". You can see this happening in the subwindow titled '''Build''' that opens up, showing the command and the output. (This window corresponds to the '''Build''' tool, so you can close and later re-open the window using the <menuchoice>Build</menuchoice> tool button on the perimeter of the main window. It is shown at the bottom right of the picture.)
for one or more of the projects in the session that we can repeatedly build
 
without much mouse work. This is where the concept of "Build target
 
selections" comes in: it is a collection of Makefile targets that are built
 
one-after-the-other whenever you hit the "Build selection" button in the
 
button list at the top, select the <menuchoice>Project > Build selection</menuchoice> menu item, or
 
hit the F8 function key.
 
  
The list of selected Makefile targets is shown in the bottom half of the
+
</translate><span id="Selecting a collection of Makefile targets for repeated building"></span><translate>
"Projects" tool view.
 
By default, the selection contains all projects, but you can change that. For
 
example, if your list of projects contains three projects (a base library L and two applications A and B), but you're currently only working on project A, then you may want to
 
remove project B from the selection by highlighting it in the selection and
 
hitting the red "-" button. Furthermore, you probably want to make sure that
 
the library L is built before  project A by moving entries in
 
the selection up and down using the buttons to the right of the list.
 
You can also get a particular Makefile target into the selection by
 
right-clicking onto it and selecting <menuchoice>Add to buildset</menuchoice>, or just highlighting
 
it and hitting the green "+" button just above the list of selected targets.
 
  
KDevelop allows you to configure what to do whenever you build the
+
=== Selecting a collection of Makefile targets for repeated building === <!--T:9-->
selection. To this end, use the menu item <menuchoice>Project > Open
 
configuration</menuchoice>. There, you can for example select the number of simultaneous
 
jobs "make" should execute &mdash; if your computer has, say, 8 processor
 
cores, then entering 8 in this field would be a useful choice. In this dialog, the "Default make target" is a Makefile target used
 
for '''all''' targets in the selection.
 
  
=== What to do with error messages ===
+
<!--T:10-->
 +
Right-clicking on individual Makefile targets every time you want to build something will quickly get old. Rather, we'd like to have individual targets for one or more of the projects in the session that we can repeatedly build without much mouse work. This is where the concept of "Build target selections" comes in: it is a collection of Makefile targets that are built one-after-the-other whenever you hit the <menuchoice>Build selection</menuchoice> button in the button list at the top, select the <menuchoice>Project -> Build selection</menuchoice> menu item, or
 +
hit the <keycap>F8</keycap> function key.
  
If the compiler encounters an error message, simply click on the line with the error message and the editor will jump to the line (and if available column) where the error was reported. Depending on the error message, KDevelop may also offer you several possible actions to fix the error, for example by declaring a previously undeclared variable if an unknown symbol was found.
+
<!--T:11-->
 +
The list of selected Makefile targets is shown in the bottom half of the '''Projects''' tool view.
 +
By default, the selection contains all projects, but you can change that. For example, if your list of projects contains three projects (a base library L and two applications A and B), but you're currently only working on project A, then you may want to remove project B from the selection by highlighting it in the selection and hitting the {{Minus}} button. Furthermore, you probably want to make sure that the library L is built before  project A by moving entries in the selection up and down using the buttons to the right of the list. You can also get a particular Makefile target into the selection by right-clicking onto it and selecting <menuchoice>Add to buildset</menuchoice>, or just highlighting it and hitting the {{Plus}} button just above the list of selected targets.
  
 +
<!--T:12-->
 +
'''KDevelop''' allows you to configure what to do whenever you build the selection. To this end, use the menu item <menuchoice>Project -> Open configuration</menuchoice>. There, you can for example select the number of simultaneous
 +
jobs "make" should execute &mdash; if your computer has, say, 8 processor cores, then entering 8 in this field would be a useful choice. In this dialog, the <menuchoice>Default make target</menuchoice> is a Makefile target used for ''all'' targets in the selection.
 +
 +
</translate><span id="What to do with error messages"></span><translate>
 +
 +
=== What to do with error messages === <!--T:13-->
 +
 +
<!--T:14-->
 +
If the compiler encounters an error message, simply click on the line with the error message or use Navigation - Jump to Next Outputmark item in the main menu and the editor will jump to the line (and if available column) where the error was reported. Depending on the error message, '''KDevelop''' may also offer you several possible actions to fix the error, for example by declaring a previously undeclared variable if an unknown symbol was found.
 +
 +
<!--T:15-->
 +
{{Prevnext2
 +
| prevpage=Special:MyLanguage/KDevelop4/Manual/Code_generation_with_templates | nextpage=Special:MyLanguage/KDevelop4/Manual/Running_programs
 +
| prevtext=Code generation with templates | nexttext=Running programs
 +
| index=Special:MyLanguage/KDevelop4/Manual | indextext=Back to menu
 +
}}
 +
 +
<!--T:16-->
 
[[Category:Development]]
 
[[Category:Development]]
 +
</translate>

Latest revision as of 11:20, 10 April 2016

Other languages:
English • ‎dansk • ‎українська

Building (compiling) projects with custom Makefiles

Many projects describe how source files have to be compiled (and which files have to be recompiled once a source or header file changes) using Makefiles that are interpreted by the make program (see, for example, GNU make). For simple projects, it is often very easy to set up such a file by hand. Larger projects often integrate their Makefiles with the GNU autotools (autoconf, autoheader, automake). In this section, let us simply assume that you have a Makefile for your project and you want to teach KDevelop how to interact with it.

Note
KDevelop 4.x doesn't know about the GNU autotools at the time this section is written. If your project uses them, you will have to run ./configure or any of the other related commands by hand on a command line. If you want to do this within KDevelop, open the Konsole tool (if necessary add it to the perimeter of the main window using the menu Windows -> Add tool view) that gives you a shell window view and run ./configure from the command line in this view.


The first step is to teach KDevelop about targets in your Makefiles. There are two ways to do that: selecting individual Makefile targets, and choosing a set of targets you may want to build frequently. For both approaches, open the Projects tool by clicking on the Projects button on the perimeter of KDevelop's main window (if you don't have this button see above how to add a tool's button there). The Projects tool window has two parts: the top half — titled Projects — lists all of your projects and let's you expand the underlying directory trees. The bottom half — titled Project Selection — lists a subset of those projects that will be built if you choose the menu item Project -> Build selection or hit F8; we'll come back to this part below.

Building individual Makefile targets

In the top part of the project view, expand the sub-tree for one project, let's say the one for which you want to run a particular Makefile target. This will give you icons for (i) directories under this project, (ii) files in the top-level directory for this project, (iii) Makefile targets KDevelop can identify. These categories are shown in the picture at right. Note that KDevelop understands Makefile syntax to a certain degree and therefore can offer you targets defined in this Makefile (though this understanding has its limits if targets are composed or implicit).

Kdevelop-1a.png

To build any of the targets listed there, click on it with the right mouse button and select Build. For example, doing this with the "clean" target will simply execute "make clean". You can see this happening in the subwindow titled Build that opens up, showing the command and the output. (This window corresponds to the Build tool, so you can close and later re-open the window using the Build tool button on the perimeter of the main window. It is shown at the bottom right of the picture.)

Selecting a collection of Makefile targets for repeated building

Right-clicking on individual Makefile targets every time you want to build something will quickly get old. Rather, we'd like to have individual targets for one or more of the projects in the session that we can repeatedly build without much mouse work. This is where the concept of "Build target selections" comes in: it is a collection of Makefile targets that are built one-after-the-other whenever you hit the Build selection button in the button list at the top, select the Project -> Build selection menu item, or hit the F8 function key.

The list of selected Makefile targets is shown in the bottom half of the Projects tool view. By default, the selection contains all projects, but you can change that. For example, if your list of projects contains three projects (a base library L and two applications A and B), but you're currently only working on project A, then you may want to remove project B from the selection by highlighting it in the selection and hitting the Icon-list-remove.png button. Furthermore, you probably want to make sure that the library L is built before project A by moving entries in the selection up and down using the buttons to the right of the list. You can also get a particular Makefile target into the selection by right-clicking onto it and selecting Add to buildset, or just highlighting it and hitting the Icon-list-add.png button just above the list of selected targets.

KDevelop allows you to configure what to do whenever you build the selection. To this end, use the menu item Project -> Open configuration. There, you can for example select the number of simultaneous jobs "make" should execute — if your computer has, say, 8 processor cores, then entering 8 in this field would be a useful choice. In this dialog, the Default make target is a Makefile target used for all targets in the selection.

What to do with error messages

If the compiler encounters an error message, simply click on the line with the error message or use Navigation - Jump to Next Outputmark item in the main menu and the editor will jump to the line (and if available column) where the error was reported. Depending on the error message, KDevelop may also offer you several possible actions to fix the error, for example by declaring a previously undeclared variable if an unknown symbol was found.


This page was last edited on 10 April 2016, at 11:20. Content is available under Creative Commons License SA 4.0 unless otherwise noted.
-->