![]() The second terminal is inside your source directory, perfect for e.g. run your ninja and ninja install commands and such. The first terminal is inside your build directory, here you can e.g. In the lower "Current Project" tool view you have per default two terminals. You will end up with a new Kate windows like shown below. If you like to have some GUI build integration, activate the build plugin, too. To have the best experience with this, ensure you have at least project & LSP plugin enabled. You can re-use this for development on any part of the KDE software stack.įor the remaining parts of this description we use Choose your Kate & KDE development directoryĬhoose yourself some path where all Kate & KDE development things should end up.īeside user local configuration files, nothing outside of this directory will be polluted. This eases contributions to all levels of the KDE software stack. Required KDE Frameworks will be compiled in addition to the Kate application parts. ![]() This avoids the need for administrator rights and allows always to fallback to use the global installed Kate if the currently build version is broken.Īs this tutorial will introduce a setup that allows to develop other parts of the KDE software stack, too, we will talk in the following about setting up a KDE development environment. ![]() This tutorial explains how to build Kate without touching your global installation.Īll stuff will happen inside an extra development directory. Right now, Kate's source code is located on the GitLab instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |