![]() 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. Choose your KDE development directoryĬhoose yourself some path where all KDE development things should end up.īeside user local configuration files, nothing outside of this directory will be polluted.įor the remaining parts of this description we useĬd ~/projects/kde/build/kde/applications/kate Now, then, let's start to illustrate how the proposed new Linux/BSD/. Kdesrc-build now has some features to automate this for you! New Kate development setup best practice do some tricks like creating the compilation database via CMake and linking it to the right place, this won't work out of the box so far. Kate learned some new tricks in the last years, too, that got not really promoted in our build setup guide: we have proper LSP support!īut if you miss to e.g. I use kdesrc-build since years for my local compiles and it is prominently promoted for e.g. kdesrc-build for the win!īeside Craft, that is very nifty to use to get stuff build, a tool that actually is in heavy use by KDE developers was somehow ignored in our beginners guide for Kate building: kdesrc-build. the package list we mention there is ancient.Īnd we didn't really outline how you can properly build the KDE Frameworks we require if you want to work on them, too. Unfortunately we didn't really keep our build description up-to-date for that, e.g. ![]() I still think the most common developer setup use case is at the moment on Linux (or fellow BSDs). recent Linux distributions.īeside that we delegate the building on e.g. On our build it page we describe how you can build Kate from kate.git manually on e.g. Still, the initial setup of a Kate/KDE development environment seems still to be an issue for a lot of beginners. No problem, this is now an own separate framework just relying on Qt. You want to use the good old Kate syntax highlighting in your project? Today, this has been split up into more manageable chunks. In the "good old" past, you had a nice thick kdelibs & kdebase repository that you did build to e.g. ![]() ![]() we merged a nice number of patches:įor more details, visit the regularly regenerated merge requests page.īeside the purely "what VCS do we use" and "which nifty web site for that" do we run, naturally the software components them-self got streamlined. We moved our code hosting to a more beginner friendly GitLab instance in the last year, too.Īnd I really think this does seem to show effects, at least for Kate & related projects we got a nice influx of contributions over GitLab.Įven just this years for Kate & Co. We traveled from ancient CVS repositories over to Subversion and since years are up and running on Git. Over the years we tried to make the development experience more pleasant and move to tools that are more widely adopted by developers around the world. Kate (and KDE) is always in need of more contributors. Sunday, 7 February 2021 | Christoph Cullmann Setup your KDE development environment - kdesrc-build & Kate
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |