https://bugs.kde.org/show_bug.cgi?id=421086

            Bug ID: 421086
           Summary: Import a project installed by kdesrc-build
           Product: kdevelop
           Version: 5.3.2
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Build tools: CMake
          Assignee: kdevelop-bugs-n...@kde.org
          Reporter: ed...@gmx.fr
  Target Milestone: ---

Importing in kdevelop the okular/CMakeLists.txt project installed through 
`kdesrc-build okular`,
code navigation failed: 
Hovering on a method or hitting Alt does not bring any information (usually, it
says where it has been defined, allowing easy navigation, it's great !)

Note: grep build-dir ~/.kdesrc-buildrc
    build-dir  /usr/local/build/kde/build  # Where the source build is run
(not in the standard place for disk space/speed/no-backup reasons)


This report shares how this has been solved, 
thanks to <frinring> help on freenode #kdevelop:

[17:31] <frinring> ederag: so in the project configuration, in the page
"CMake", 
at the top you want to have the entry pointing to the toplevel build dir of
okular you use with kdesrc-build.

That's the directory shown by
grep build-dir ~/.kdesrc-buildrc

Now all the variables point to the /usr/local/build/kde ... great !
And a few minutes later (5-15 min ?), the semantic highlighting just came on.
code navigation works !


Now configure the launch:

workaround https://bugs.kde.org/show_bug.cgi?id=420630#c1
Settings > configure kdevelop > Environment > profile > Add "kde"
add a line with
variable: QT_PLUGIN_PATH
value: /usr/local/build/kde/install/lib64/plugins

run > Configure Launches > Add > choose a name, e.g. 'kdesrc-build run'

Script interpreter: perl

Always run the same file :
file:///home/ederag/share/prog/kde/kdesrc-build/kdesrc-build

Arguments:
--run okular

Environment: kde (the one created above)

since the launch passes through a script, the process has to be attached
manually:
https://docs.kde.org/trunk5/en/extragear-kdevelop/kdevelop/attaching-the-debugger-to-a-running-process.html


Of course it could be possible to add these instructions, e.g. in
https://docs.kde.org/trunk5/en/extragear-kdevelop/kdevelop/setting-up-a-session-and-importing-an-existing-project.html#option-2--importing-a-project-that-is-
already-on-your-hard-drive
but it would be great if this could be integrated into the wizard itself.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to