File: README.md

package info (click to toggle)
kdevelop 4%3A25.04.0-1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 73,508 kB
  • sloc: cpp: 291,803; python: 4,322; javascript: 3,518; sh: 1,316; ansic: 703; xml: 414; php: 95; lisp: 66; makefile: 31; sed: 12
file content (35 lines) | stat: -rw-r--r-- 1,516 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
# Simple KDevelop Plugin

## Installation instructions

Make sure the project is configured to install to the directory of your choice:

In KDevelop, select the menu entry "Project" > "Open Configuration...",
then in the dialog choose the tab "CMake",
there select in the "Cache Values" list the entry with the name `CMAKE_INSTALL_PREFIX`
and ensure the correct path is set.

If you install to a custom directory, you need to extend the `QT_PLUGIN_PATH`
environment variable that KDevelop sees when it is started. The path to be added
is the "plugins" subdir, whose exact path depends on the operating system and
if that is a 64 bit or 32 bit one.
On Debian, Ubuntu & similar with a 64 bit system add:
    $my_install_prefix/lib/x86_64-linux-gnu/plugins
On openSUSE & similar with a 64 bit system add:
    $my_install_prefix/lib64/plugins
(where `$my_install_prefix` is the directory `CMAKE_INSTALL_PREFIX` is set to)

If you are unsure, check in the installation log the path to which the plugin is installed.


Example:
When CMAKE_INSTALL_PREFIX is set to "/home/userX/projects/mykdevplugin/" and
this is a Debian 64-bit system, open a console and enter:

    export QT_PLUGIN_PATH=$QT_PLUGIN_PATH:/home/userX/projects/mykdevplugin/lib/x86_64-linux-gnu/plugins 

Then start KDevelop from that console:

    kdevelop

If 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".