Difference between revisions of "Development/Tools/fr"

(Created page with "== Debogage et analyse ==")
(Created page with "== Environnements de développement et éditeurs ==")
 
(8 intermediate revisions by the same user not shown)
Line 19: Line 19:
 
: Some KDE projects still use [[Community:Infrastructure/Subversion|Subversion]] for some things, notably translations. Third-party developers mostly don't need to bother with this but contributors should take note of it.
 
: Some KDE projects still use [[Community:Infrastructure/Subversion|Subversion]] for some things, notably translations. Third-party developers mostly don't need to bother with this but contributors should take note of it.
  
== Development Environments and Editors ==
+
== Environnements de développement et éditeurs ==
  
; Qt Creator
+
== Assurance qualité ==
  
 
: Qt application developers are most likely already using Qt Creator as their IDE. The good news is that they don't need to switch away from it just to use KDE Frameworks. Simply add the appropriate module to the QMake project file as indicated by each one's API documentation and you're good to go.
 
: Qt application developers are most likely already using Qt Creator as their IDE. The good news is that they don't need to switch away from it just to use KDE Frameworks. Simply add the appropriate module to the QMake project file as indicated by each one's API documentation and you're good to go.
Line 45: Line 45:
 
: [http://sources.redhat.com/gdb/ GDB] helps in debugging source code. A graphical frontend, like the two below, might be a preferable way to use this tool.
 
: [http://sources.redhat.com/gdb/ GDB] helps in debugging source code. A graphical frontend, like the two below, might be a preferable way to use this tool.
  
; KDbg and DDD
+
; KDbg et DDD
  
 
: [http://www.kdbg.org/ KDbg] and [http://www.gnu.org/software/ddd/ DDD] are graphical user interfaces to GDB, which are able to set breakpoints, step through the code, etc.
 
: [http://www.kdbg.org/ KDbg] and [http://www.gnu.org/software/ddd/ DDD] are graphical user interfaces to GDB, which are able to set breakpoints, step through the code, etc.
Line 51: Line 51:
 
For some tips on KDE software analysis and profiling, please visit the [[Community:Guidelines_and_HOWTOs/Debugging|Debugging page]] of the KDE Community Wiki.
 
For some tips on KDE software analysis and profiling, please visit the [[Community:Guidelines_and_HOWTOs/Debugging|Debugging page]] of the KDE Community Wiki.
  
== Translation ==
+
== Traduction ==
  
 
Most Qt projects use the framework's built-in translation system. For KDE projects, please see the [[Community:Guidelines_and_HOWTOs/Internationalization|Community Internationalization Guide]].
 
Most Qt projects use the framework's built-in translation system. For KDE projects, please see the [[Community:Guidelines_and_HOWTOs/Internationalization|Community Internationalization Guide]].
  
== Helper Tools ==
+
== Outils d'aide ==
  
 
Here are some command-line tools that can assist developers in some of their day-to-day tasks.
 
Here are some command-line tools that can assist developers in some of their day-to-day tasks.
Line 69: Line 69:
 
;[[Development/Tools/Using kconf_update|kconf_update]]
 
;[[Development/Tools/Using kconf_update|kconf_update]]
  
: Automates updating config files.
+
: Automates pour mettre à jour les fichiers de configuration.
  
 
;[[Development/Tools/apidox|kapidox]]
 
;[[Development/Tools/apidox|kapidox]]
Line 75: Line 75:
 
: Generates API documentation for Doxygen-marked code.
 
: Generates API documentation for Doxygen-marked code.
  
== Quality Assurance ==
+
== Assurance qualité ==
  
 
KDE contributors and third-party developers interested in monitoring the community's software development activities can take a peek via the sites and tools below.
 
KDE contributors and third-party developers interested in monitoring the community's software development activities can take a peek via the sites and tools below.
  
;Project Management
+
;Gestion de projet
  
 
: KDE currently uses [https://phabricator.kde.org/ Phabricator] for project management but is also moving to a [https://invent.kde.org/ Gitlab instance].
 
: KDE currently uses [https://phabricator.kde.org/ Phabricator] for project management but is also moving to a [https://invent.kde.org/ Gitlab instance].
  
;Continuous Building
+
;Intégration continue
  
 
: To ensure high-quality, KDE software operates a [http://build.kde.org continuous integration system] powered by [https://jenkins.io/ Jenkins].
 
: To ensure high-quality, KDE software operates a [http://build.kde.org continuous integration system] powered by [https://jenkins.io/ Jenkins].
  
;Static Analysis
+
;Analyse statique
  
 
: KDE uses an automated static analysis tool hosted on the [http://ebn.kde.org/ English Breakfast Network]
 
: KDE uses an automated static analysis tool hosted on the [http://ebn.kde.org/ English Breakfast Network]

Latest revision as of 17:52, 7 September 2020

Other languages:
English • ‎français • ‎português do Brasil • ‎українська

The KDE Community produces libraries and tools for software development but, aside from Qt and CMake, doesn't prescribe which one to use. Here is just a sample of the various tools you can use when developing software that uses KDE APIs or contributing to KDE applications themselves.

Outils du noyau

These are the tools that are absolutely required to build and develop KDE software. On Linux, they will typically be provided by your distribution. On other platforms, packages should normally be available, often for download directly from the home page for the tool. Of course, the standard development tools, such as a C/C++ compiler and some sort of text editor, are also required.

CMake
CMake is KDE's build system of choice. Once you have this, you can use it to configure a software project for building, and that process will tell you of any other requirements you are missing. NOTE: KDE Frameworks can also be used in QMake-based projects.
Git
Most KDE projects are developed in Git, and so you will need it to get the latest development version of the source code. KDE also provides source code tarballs for the most recent releases. You can find the relevant Git URLs at the KDE Git repository browser.
Subversion
Some KDE projects still use Subversion for some things, notably translations. Third-party developers mostly don't need to bother with this but contributors should take note of it.

Environnements de développement et éditeurs

Assurance qualité

Qt application developers are most likely already using Qt Creator as their IDE. The good news is that they don't need to switch away from it just to use KDE Frameworks. Simply add the appropriate module to the QMake project file as indicated by each one's API documentation and you're good to go.
KDevelop
KDevelop is a powerful IDE for developing KDE and Qt C++ applications. Unlike Qt Creator, however, it isn't limited to just that use case and supports other languages, libraries, and tools as well.
Kate
Although not exactly an IDE, KDE's premiere Advanced Text Editor has features and plugins that simplify the software development workflow, from syntax highlighting and code folding to project management to an embedded terminal emulator.

Debogage et analyse

There is a wide variety of tools available, especially on Linux that analyze code and profile applications. Here are some of the more popular ones.

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. A graphical frontend, like the two below, might be a preferable way to use this tool.
KDbg et DDD
KDbg and DDD are graphical user interfaces to GDB, which are able to set breakpoints, step through the code, etc.

For some tips on KDE software analysis and profiling, please visit the Debugging page of the KDE Community Wiki.

Traduction

Most Qt projects use the framework's built-in translation system. For KDE projects, please see the Community Internationalization Guide.

Outils d'aide

Here are some command-line tools that can assist developers in some of their day-to-day tasks.

kf5-config
Provides information related to the installation of KDE libraries and applications, particularly paths and prefixes.
kioclient5
Performs network-transparent operations (via the KIO framework) on the command line, like copying or even downloading files.
kconf_update
Automates pour mettre à jour les fichiers de configuration.
kapidox
Generates API documentation for Doxygen-marked code.

Assurance qualité

KDE contributors and third-party developers interested in monitoring the community's software development activities can take a peek via the sites and tools below.

Gestion de projet
KDE currently uses Phabricator for project management but is also moving to a Gitlab instance.
Intégration continue
To ensure high-quality, KDE software operates a continuous integration system powered by Jenkins.
Analyse statique
KDE uses an automated static analysis tool hosted on the English Breakfast Network

This page was last edited on 7 September 2020, at 17:52. Content is available under Creative Commons License SA 4.0 unless otherwise noted.