< Guidelines and HOWTOs Revision as of 12:46, 11 February 2018 (view source)Yurchor (talk | contribs)m (Fix typos)← Older edit Revision as of 16:22, 28 February 2018 (view source) Harmathy (talk | contribs) m (→Build from source: Add basic explanation)Newer edit → Line 2: Line 2: == Build from source == == Build from source == ; [[Guidelines and HOWTOs/Build_from_source| Build from source]] ; [[Guidelines and HOWTOs/Build_from_source| Build from source]] +: How to set up your environment to build and start developing KDE software. == Best practices == == Best practices == Revision as of 16:22, 28 February 2018 Let's development together with Konqi! Contents 1 Build from source 2 Best practices 3 Core Tools 4 Debugging and Analysis 5 Important Tutorials 6 Integrated Development Environment (IDE) Build from source Build from source How to set up your environment to build and start developing KDE software. Best practices UnitTests A guide to correctly do your unit tests. Because you never push code which is not unit tested! -- Tutorial by Brad Hards that describes how to write unit tests using the QTestLib framework. Detect code errors Semi-automatic way to detect code errors based on Krazy. (related: EBN) API Documentation How to write good API documentation (related: https://api.kde.org). Core Tools 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. Git Most KDE projects are developed in Git, and so you will need it to get the source code in the first place. You can find the relevant Git URLs in the KDE projects directory. It will be helpful to follow the git how to. Subversion KDE still uses Subversion for some things, notably translations. Debugging and Analysis A list of tools which are used to analyze a program. This includes debuggers and profilers, for instance, GDB, Valgrind,... More on the debugging page... Important Tutorials KDE Frameworks 5 porting notes. Wayland porting notes. Making applications and automatic tests run uninstalled Integrated Development Environment (IDE) Qt Creator With Qt Creator it is easy to write new KDE based programs and to integrate existing ones into an IDE. Further details can be found in the tutorial Using Qt Creator. KDevelop KDevelop is an IDE for developing KDE and Qt C++ applications. It includes 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. Further details can also be found in the wiki. Eclipse It is possible to develop C++, Qt and KDE software using Eclipse as your IDE. Further details can be found on the Eclipse page. CLion CLion is a cross-platform IDE from JetBrains. It uses CMake as a build tool, so you can easily continue developing any project which is built with it. CLion has powerful auto-complete, code-generation and refactoring features. It also provides an integrated debugger (GDB or LLDB) and an embedded terminal. MS Visual Studio® Express IDE (Windows only) Visual C++® Express is the free version of the Microsoft Visual Studio compiler from Microsoft, which is officially supported by Nokia. It is a choice for compiling Qt and KDE applications on Windows. more info... Retrieved from "https://community.kde.org/index.php?title=Guidelines_and_HOWTOs/Development&oldid=79595" Content is available under Creative Commons License SA 4.0 unless otherwise noted.