• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..27-Feb-2022-

src/H03-May-2022-4530

%{PROJECTDIRNAME}.kdev4H A D27-Feb-202251 43

README.mdH A D27-Feb-20221.5 KiB3624

cmake_kdevplugin.kdevtemplateH A D27-Feb-20223.1 KiB5857

README.md

1# Simple KDevelop Plugin
2
3## Installation instructions
4
5Make sure the project is configured to install to the directory of your choice:
6
7In KDevelop, select the menu entry "Project" > "Open Configuration...",
8then in the dialog choose the tab "CMake",
9there select in the "Cache Values" list the entry with the name `CMAKE_INSTALL_PREFIX`
10and ensure the correct path is set.
11
12If you install to a custom directory, you need to extend the `QT_PLUGIN_PATH`
13environment variable that KDevelop sees when it is started. The path to be added
14is the "plugins" subdir, whose exact path depends on the operating system and
15if that is a 64 bit or 32 bit one.
16On Debian, Ubuntu & similar with a 64 bit system add:
17    $my_install_prefix/lib/x86_64-linux-gnu/plugins
18On openSUSE & similar with a 64 bit system add:
19    $my_install_prefix/lib64/plugins
20(where `$my_install_prefix` is the directory `CMAKE_INSTALL_PREFIX` is set to)
21
22If you are unsure, check in the installation log the path to which the plugin is installed.
23
24
25Example:
26When CMAKE_INSTALL_PREFIX is set to "/home/userX/projects/mykdevplugin/" and
27this is a Debian 64-bit system, open a console and enter:
28
29    export QT_PLUGIN_PATH=$QT_PLUGIN_PATH:/home/userX/projects/mykdevplugin/lib/x86_64-linux-gnu/plugins
30
31Then start KDevelop from that console:
32
33    kdevelop
34
35If everything went well, you should see "Hello world, my plugin is loaded!" printed in the console and find the plugin also listed in the dialog opened by the menu entry "Help" > "Loaded Plugins".
36