Difference between revisions of "Development/Tools"

Jump to: navigation, search
(remove gprof and kprof (last change 1998!) valgrind does it all.)
Line 1: Line 1:
__TOC__
 
 
This section contains information about tools for KDE development.
 
This section contains information about tools for KDE development.
==Analysis==
+
 
A list of tools which are used to analyze a program. This would include debuggers and profilers, for instance.
+
== Analysis ==
=== [http://valgrind.kde.org/ Valgrind] ===
+
A list of tools which are used to analyze a program. This includes debuggers and profilers, for instance.
A tool for searching memory leaks and/or uninitialized memory. Also includes a profiler. Valgrind is surely one of the most important development tools!
+
 
=== [http://sources.redhat.com/gdb/ The GNU Project Debugger (GDB)]===
+
=== Valgrind ===
Sooner or later you may need a debugger. Here is one (probably gdb is already shipped with your distribution). You should use at least version 4.95. There are also grahpical frontends available for gdb (see below).
+
[http://www.valgrind.org/ Valgrind] helps to find memory leaks and uninitialized memory blocks. Additional features are a profiler and more. Valgrind is one of the most important development tools!
See also the [http://developer.kde.org/documentation/other/gdb-doc.html KDE GDB Debugging HOWTO]
+
 
=== [http://members.nextra.at/johsixt/kdbg.html KDbg] ===
+
=== The GNU Project Debugger (GDB) ===
A graphical user interface to gdb, which is able to set breakpoints, step through the code and so on.
+
[http://sources.redhat.com/gdb/ GDB] helps in debugging source code. As GDB evolved over time it is recommended to use version 6.x. Graphical frontends are available (see below). See also the [[Howto/GDB Debugging HOWTO|GDB debugging howto]]
=== [http://www.gnu.org/software/binutils/manual/gprof-2.9.1/gprof.html The GNU Profiler (GProf)] ===
+
<!--TODO: migrate [http://developer.kde.org/documentation/other/gdb-doc.html KDE GDB Debugging HOWTO]-->
GProf is a profiler which is able to display which function takes how much time, how often it is called and so on. There is also a KDE frontend available which takes the same data files as the gprof command does. See below.
+
 
=== [http://kprof.sourceforge.net/ KProf] ===
+
=== KDbg ===
KProf is a tool that displays execution profiling generated by various code profilers (among them the GNU Profiler).
+
[http://www.kdbg.org/ KDbg] is a graphical user interface to GDB, which is able to set breakpoints, step through the code etc.
 +
 
 
== KDevelop ==
 
== KDevelop ==
This is a superb IDE for developing KDE and Qt C++ applications. It includes a an integrated debugger, a syntax highlighting editor, and of course a 'Project wizard' to handle the creation of the basic menu structures, the automake/autoconf gunk, and even the class documentation. For more details, see: [http://www.kdevelop.org/ http://www.kdevelop.org/]
+
[http://www.kdevelop.org KDevelop] is an excellent IDE for developing KDE and Qt C++ applications. It includes a an integrated debugger, a powerful editor with syntax highlighting, a ''Project wizard'' to create applications from templates, the automake/autoconf gunk, and even the class documentation.
==Qt Designer==
+
 
The user interface designer that comes with Qt. Supports layout management, undo/redo, checking accelerator conflicts etc. etc. This is a tool that allows even non-programmers to help design dialogs of KDE applications.
+
== Qt Designer ==
For more details, see the [http://www.trolltech.com/products/qt/designer.html official website].
+
With Trolltechs [http://www.trolltech.com/products/qt/features/designer Qt Designer] it is easy to layout user interfaces like buttons and checkboxes. Additional features are undo/redo, checking accelerator conflicts etc. Qt Designer allows even non-programmers to help design KDE dialogs.
==i18n tools==
+
 
 +
== i18n Tools ==
 
You can find information on writing and translating documentation on [http://i18n.kde.org/ this dedicated site].
 
You can find information on writing and translating documentation on [http://i18n.kde.org/ this dedicated site].

Revision as of 16:55, 10 September 2006

This section contains information about tools for KDE development.

Contents

Analysis

A list of tools which are used to analyze a program. This includes debuggers and profilers, for instance.

Valgrind

Valgrind helps to find memory leaks and uninitialized memory blocks. Additional features are a profiler and more. Valgrind is one of the most important development tools!

The GNU Project Debugger (GDB)

GDB helps in debugging source code. As GDB evolved over time it is recommended to use version 6.x. Graphical frontends are available (see below). See also the GDB debugging howto

KDbg

KDbg is a graphical user interface to GDB, which is able to set breakpoints, step through the code etc.

KDevelop

KDevelop is an excellent IDE for developing KDE and Qt C++ applications. It includes a an integrated debugger, a powerful editor with syntax highlighting, a Project wizard to create applications from templates, the automake/autoconf gunk, and even the class documentation.

Qt Designer

With Trolltechs Qt Designer it is easy to layout user interfaces like buttons and checkboxes. Additional features are undo/redo, checking accelerator conflicts etc. Qt Designer allows even non-programmers to help design KDE dialogs.

i18n Tools

You can find information on writing and translating documentation on this dedicated site.


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal