|
|
| (12 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| If you have any trouble getting things to build due to missing 3rd-party package dependencies, read on to learn what to do. If you need help, see https://community.kde.org/Get_Involved#Contacting_The_Community.
| | See https://develop.kde.org/docs/getting-started/building/help-dependencies |
| | |
| == How to install the dependencies of one package ==
| |
| === KDE neon, Debian, Ubuntu, Kubuntu ===
| |
| All the build packages known by the package you want to build can be installed by running:
| |
| | |
| <code>sudo apt build-dep <package you want to build></code>
| |
| | |
| For example, to install the build dependencies for Dolphin, run:
| |
| | |
| <code>sudo apt build-dep dolphin</code>
| |
| | |
| === Fedora ===
| |
| If dependencies are missing for a specific RPM package, you can run:
| |
| | |
| <code>sudo dnf builddep <name_of_rpm_package></code>
| |
| | |
| For example, to install the build dependencies for Dolphin, run:
| |
| | |
| <code>sudo dnf builddep dolphin</code>
| |
| | |
| === openSUSE ===
| |
| Generally you can install the required -devel packages that are needed to build some KDE software from source by using <code>zypper</code> (as root, or by using <code>sudo</code>), e.g. to install the -devel packages required to build dolphin from source:
| |
| {{Input|1=<nowiki>
| |
| # zypper --plus-content repo-source source-install --build-deps-only dolphin
| |
| </nowiki>}}
| |
| | |
| replace ''dolphin'' with some other package name, e.g. to build ''ktexteditor'' from source:
| |
| {{Input|1=<nowiki>
| |
| # zypper --plus-content repo-source source-install --build-deps-only ktexteditor
| |
| </nowiki>}}
| |
| | |
| Note that the <code>--plus-content</code> option in the above commands means you don't need to have the source repository enabled all the time, <code>--plus-content</code> will make zypper temporarily enable it to get the info it needs.
| |
| | |
| openSUSE (and most other RPM-based Linux distributions) support cmake() BuildRequires, which means you can install a development package like so:
| |
| {{Input|1=<nowiki>
| |
| # zypper install 'cmake(KF5KIO)'
| |
| </nowiki>}}
| |
| | |
| the part between the parenthesis ''KF5KIO'' is going to be in the error message that CMake will print in the terminal if you try to build something that requires e.g. KIO if KIO development headers aren't installed.
| |
| | |
| Any other dependencies can be figured out and installed as you continue building the modules one by one.
| |
| | |
| == Fix CMake Error ==
| |
| | |
| If the CMake error looks like:
| |
| <pre>
| |
| Build-time dependency gi-docgen found: NO (tried pkgconfig and cmake)
| |
| | |
| docs/api/meson.build:5:15: ERROR: Dependency "gi-docgen" not found, tried pkgconfig and cmake
| |
| </pre>
| |
| | |
| The error here is that CMake could not find the pkgconfig named "gi-docgen" (most probably a file with the extension".pc") or the CMake file (most probably a file with the extension".cmake") that contains "gi-docgen" case insensitively in name.
| |
| | |
| Fedora
| |
| | |
| * Maybe we can find the correct package name.
| |
| | |
| <pre>
| |
| # Is there an rpm package with the name "gi-docgen" installed?
| |
| rpm -qa gi-docgen
| |
| # It is not installed.
| |
| | |
| # Is there in the package repositories an rpm with name containing "gi-docgen"?
| |
| dnf search gi-docgen
| |
| # Returns:
| |
| # Last metadata expiration check: ...
| |
| #============================================================================== Name #Exactly Matched: gi-docgen #==============================================================================
| |
| #gi-docgen.noarch : Documentation tool for GObject-based libraries
| |
| #============================================================================= Name & #Summary Matched: gi-docgen #=============================================================================
| |
| #gi-docgen-doc.noarch : Documentation for gi-docgen
| |
| #gi-docgen-fonts.noarch : Metapackage providing fonts for gi-docgen output
| |
| | |
| # Install the rpm gi-docgen
| |
| dnf install gi-docgen
| |
| </pre>
| |
| | |
| * Look for the .pc or .cmake file in the content of all rpm files in all of the enabled package repositories.
| |
| | |
| <pre>
| |
| dnf repoquery -l gi-docgen
| |
| # Returns:
| |
| #/usr/bin/gi-docgen
| |
| #...
| |
| #/usr/share/pkgconfig/gi-docgen.pc
| |
| | |
| dnf install gi-docgen
| |
| </pre>
| |
| | |
| * DNF knows how to install the rpm that contains a given pkgconfig file.
| |
| | |
| <pre>
| |
| dnf provides 'pkgconfig(gi-docgen)'
| |
| # Returns:
| |
| #gi-docgen-2023.1-9.fc39.noarch : Documentation tool for GObject-based libraries
| |
| #Repo : fedora
| |
| #Matched from:
| |
| #Provide : pkgconfig(gi-docgen) = 2023.1
| |
| sudo dnf install 'pkgconfig(gi-docgen)'
| |
| </pre>
| |
