... | ... | @@ -8,17 +8,17 @@ Some KDE community guidelines: |
|
|
|
|
|
KMyMoney requires several components to be accessible to run (and debug) successfully:
|
|
|
|
|
|
* icons and other media (solved in master by having the [icons embedded into binaries](#packaging-specifics).)
|
|
|
* icons and other media (solved in master by having the [icons embedded into binaries](Coding-conventions#packaging-specifics).)
|
|
|
* stylesheets, QML files, etc. (solved in [#33](https://invent.kde.org/office/kmymoney/-/issues/33))
|
|
|
* Qt plugins
|
|
|
|
|
|
Traditionally running `make install` with root permissions would place these at correct locations on all systems, but, [as explained](#compilation), this is advised against. Instead, you should be able to debug [in-place (uninstalled)](#debugging-in-place-uninstalled) or [after a local installation](#debugging-after-a-local-installation).
|
|
|
Traditionally running `make install` with root permissions would place these at correct locations on all systems, but, [as explained](Compilation), this is advised against. Instead, you should be able to debug [in-place (uninstalled)](#debugging-in-place-uninstalled) or [after a local installation](#debugging-after-a-local-installation).
|
|
|
|
|
|
## Debugging in-place (uninstalled)
|
|
|
|
|
|
It is possible to debug KMyMoney simply by building the code and running the executable.
|
|
|
|
|
|
This, however, requires building the plugins statically. Refer to the [CMake switches](#CMake-switches) section for details.
|
|
|
This, however, requires building the plugins statically. Refer to the [CMake switches](Compilation#cmake-switches) section for details.
|
|
|
|
|
|
Also, this won't fully work in 5.1 branch because of the resources that it loads directly from the filesystem, as opposed to QRC which master uses.
|
|
|
|
... | ... | |