Finding Build Dependencies

Brucehankins

Have a question about finding dependencies for an application. I looked through some online tutorials, but haven't found the answer yet. Here's what I'm trying to do, I'm trying to build and package the .eopkg for backup. I was able to build and install it from source, but now I want to try and package it into a .eopkg.
I've gotten to setting up the package.yml file, but I'm not sure what the build dependencies are or how to find them since I installed it from Github and not the Solus repos. I've checked the .spec file , the read.me and the copying file, but I'm not sure where to go. Any guidance on where to look would be great.

FYI, trying to do this while currently using Solus Plasma 4.2.

Brucehankins

Found most of what I need I believe in CMakeLists.txt. The package names a slightly different, like I18n is ki18n in our repos. There were two I was unsure of, but I'm hoping they're part of qt5-base and qt5-base-devel.
The two I'm really not sure about are
find_package(Qt5 ${QT_MIN_VERSION} CONFIG REQUIRED COMPONENTS Core Widgets

Brucehankins

So I was able to create the package.yml file correctly I'm pretty sure. Now I'm running into errors when I execute sudo solbuild build package.yml -p main-x86_64 It says build failed error="exit status 1".

Harvey

Finding the build and run dependencies can be a real PITA. Sometimes things are well documented by the developer and missing dependency errors are clear other times you go hunting. Not every application uses the same build system so there will not always be a CMakeLists.txt however it seems like you're figuring this stuff out well enough.

Did you read the official documentation on packaging for Solus? Which covers everything from setting up the build environment to creating / updating packages: https://getsol.us/articles/packaging/

"exit status 1" is not a particularly helpful error. It just means it failed, it doesn't give any hint as to the reason why. So the actual error may be elsewhere in the log.

EDIT:
If someone were to attempt to help you with this task, they are going to need to know exactly what you're packaging. Seeing your package.yml wouldn't hurt either.

Brucehankins

Harvey Here is the latest attempt

and the attempt before I added the additional info to build and install

and here is the last bit of the output from the CMakeOutput.log file.
`Determining if the GLIBC exist passed with the following output:
Change Dir: /home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/gmake cmTC_49370/fast && /usr/bin/gmake -f CMakeFiles/cmTC_49370.dir/build.make CMakeFiles/cmTC_49370.dir/build
gmake[1]: Entering directory '/home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_49370.dir/CheckSymbolExists.c.o
/usr/lib64/ccache/bin/x86_64-solus-linux-gcc -mtune=generic -march=x86-64 -g2 -O2 -pipe -fPIC -Wformat -Wformat-security -D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=32 -fasynchronous-unwind-tables -ftree-vectorize -feliminate-unused-debug-types -Wall -Wno-error -Wp,-D_REENTRANT -o CMakeFiles/cmTC_49370.dir/CheckSymbolExists.c.o -c /home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp/CheckSymbolExists.c
Linking C executable cmTC_49370
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_49370.dir/link.txt --verbose=1
/usr/lib64/ccache/bin/x86_64-solus-linux-gcc -mtune=generic -march=x86-64 -g2 -O2 -pipe -fPIC -Wformat -Wformat-security -D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=32 -fasynchronous-unwind-tables -ftree-vectorize -feliminate-unused-debug-types -Wall -Wno-error -Wp,-D_REENTRANT -Wl,--copy-dt-needed-entries -Wl,-O1 -Wl,-z,relro -Wl,-z,now -Wl,-z,max-page-size=0x1000 -Wl,-Bsymbolic-functions -Wl,--sort-common CMakeFiles/cmTC_49370.dir/CheckSymbolExists.c.o -o cmTC_49370
gmake[1]: Leaving directory '/home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp'

File /home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include <stdlib.h>

int main(int argc, char** argv)
{
(void)argv;
#ifndef GLIBC
return ((int*)(&GLIBC))[argc];
#else
(void)argc;
return 0;
#endif
}
Performing C++ SOURCE FILE Test _OFFT_IS_64BIT succeeded with the following output:
Change Dir: /home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/gmake cmTC_2d79b/fast && /usr/bin/gmake -f CMakeFiles/cmTC_2d79b.dir/build.make CMakeFiles/cmTC_2d79b.dir/build
gmake[1]: Entering directory '/home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_2d79b.dir/src.cxx.o
/usr/lib64/ccache/bin/x86_64-solus-linux-g++ -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -D_OFFT_IS_64BIT -mtune=generic -march=x86-64 -g2 -O2 -pipe -fPIC -D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=32 -fasynchronous-unwind-tables -ftree-vectorize -feliminate-unused-debug-types -Wall -Wno-error -Wp,-D_REENTRANT -o CMakeFiles/cmTC_2d79b.dir/src.cxx.o -c /home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp/src.cxx
Linking CXX executable cmTC_2d79b
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_2d79b.dir/link.txt --verbose=1
/usr/lib64/ccache/bin/x86_64-solus-linux-g++ -mtune=generic -march=x86-64 -g2 -O2 -pipe -fPIC -D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=32 -fasynchronous-unwind-tables -ftree-vectorize -feliminate-unused-debug-types -Wall -Wno-error -Wp,-D_REENTRANT -Wl,--copy-dt-needed-entries -Wl,-O1 -Wl,-z,relro -Wl,-z,now -Wl,-z,max-page-size=0x1000 -Wl,-Bsymbolic-functions -Wl,--sort-common CMakeFiles/cmTC_2d79b.dir/src.cxx.o -o cmTC_2d79b
gmake[1]: Leaving directory '/home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp'

Source file was:

#include <sys/types.h>
/* Check that off_t can represent 2**63 - 1 correctly.
We can't simply define LARGE_OFF_T to be 9223372036854775807,
since some C++ compilers masquerading as C compilers
incorrectly reject 9223372036854775807. */
#define LARGE_OFF_T (((off_t) 1 << 62) - 1 + ((off_t) 1 << 62))
int off_t_is_large[(LARGE_OFF_T % 2147483629 == 721 && LARGE_OFF_T % 2147483647 == 1) ? 1 : -1];
int main() { return 0; }

Performing C++ SOURCE FILE Test HAVE_DATE_TIME succeeded with the following output:
Change Dir: /home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/gmake cmTC_5ba8b/fast && /usr/bin/gmake -f CMakeFiles/cmTC_5ba8b.dir/build.make CMakeFiles/cmTC_5ba8b.dir/build
gmake[1]: Entering directory '/home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_5ba8b.dir/src.cxx.o
/usr/lib64/ccache/bin/x86_64-solus-linux-g++ -DHAVE_DATE_TIME -mtune=generic -march=x86-64 -g2 -O2 -pipe -fPIC -D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=32 -fasynchronous-unwind-tables -ftree-vectorize -feliminate-unused-debug-types -Wall -Wno-error -Wp,-D_REENTRANT -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time -o CMakeFiles/cmTC_5ba8b.dir/src.cxx.o -c /home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp/src.cxx
Linking CXX executable cmTC_5ba8b
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_5ba8b.dir/link.txt --verbose=1
/usr/lib64/ccache/bin/x86_64-solus-linux-g++ -mtune=generic -march=x86-64 -g2 -O2 -pipe -fPIC -D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=32 -fasynchronous-unwind-tables -ftree-vectorize -feliminate-unused-debug-types -Wall -Wno-error -Wp,-D_REENTRANT -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wl,--enable-new-dtags -Wl,--copy-dt-needed-entries -Wl,-O1 -Wl,-z,relro -Wl,-z,now -Wl,-z,max-page-size=0x1000 -Wl,-Bsymbolic-functions -Wl,--sort-common CMakeFiles/cmTC_5ba8b.dir/src.cxx.o -o cmTC_5ba8b
gmake[1]: Leaving directory '/home/build/YPKG/root/kbackup/build/kbackup-master/CMakeFiles/CMakeTmp'

Source file was:
int main() { return 0; }`

Brucehankins

Packaging kbackup, I'll post a screenshot of the package.yml file. I pulled the .log file also, but I really don't know what I'm looking at yet, still learning.

Harvey

If this is something you decide you want start doing for yourself or contributing you'll start recognising these errors with time.

You can look at the CmakeLists.txt or similar files for hints if they're not explictly listed in the README.md, but I'm going to do what I usually do an work blind.

First error I encountered was:

CMake Error at CMakeLists.txt:14 (find_package):
  Could not find a package configuration file provided by "ECM" (requested
  version 5.71.0) with any of the following names:

    ECMConfig.cmake
    ecm-config.cmake

  Add the installation prefix of "ECM" to CMAKE_PREFIX_PATH or set "ECM_DIR"
  to a directory containing one of the above files.  If "ECM" provides a
  separate development package or SDK, be sure it has been installed.

I'll stop working blind for a second just illustrate how vague it can be. CMakeLists.txt reference to this is:

find_package(ECM ${KF5_MIN_VERSION} REQUIRED NO_MODULE)

You probably still have no idea what that means. But ECM is refering to extra-cmake-modules

Okay so I add that and the next error was:

CMake Error at /usr/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:218 (message):
  Could NOT find KF5 (missing: Notifications I18n KIO DocTools XmlGui
  IconThemes Archive WidgetsAddons) (Required is at least version "5.71.0")
Call Stack (most recent call first):
  /usr/share/cmake-3.19/Modules/FindPackageHandleStandardArgs.cmake:582 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/ECM/find-modules/FindKF5.cmake:94 (find_package_handle_standard_args)
  CMakeLists.txt:31 (find_package)

Lot of stuff missing. If you don't know the package name search for it and hope its in the repo, as you've realised things may be named slightly differently so don't be too specific with the search.

So based on only that info I have added these builddeps:

extra-cmake-modules
karchive-devel
kdoctools-devel
ki18n-devel
kiconthemes-devel
kio-devel
knotifications-devel
kwidgetsaddons-devel
kxmlgui-devel

If this was being worked on for submission for inclusion in the Solus repository you have more work to do cleaning up. When you add things to the builddeps you should check that package dependencies using eopkg info packagename You'll often find builddeps that depend on other builddeps. If so you don't need to explicitly state that builddep as it'll be pulled in anyway.

Example I can remove ki18n-devel and kxmlgui-devel because kio-devel has those as dependencies. I can remove extra-cmake-modules as well as karchive-devel depends on that. qt5-base-devel is depended on by lots of stuff.. etc etc and it ends up like this:

name       : kbackup
version    : 20.12.2
release    : 1
source     :
    - https://invent.kde.org/utilities/kbackup/-/archive/v20.12.2/kbackup-v20.12.2.tar.gz : 269ea46f684902301e66cc86dd7876acf23fde41a86f9d79c9e3631f98339bf8
license    : GPL-2.0-or-later
component  : system.utils
summary    : kbackup is a qt backup program with an easy to use interface
description: |
    kbackup is a qt backup program with an easy to use interface
builddeps  :
    - karchive-devel
    - kdoctools-devel
    - kiconthemes-devel
    - kio-devel
    - knotifications-devel
setup      : |
    %cmake_ninja
build      : |
    %ninja_build
install    : |
    %ninja_install

The above compiles successfully but I haven't tested if it runs. If it doesn't you may need to work on figuring out run dependencies.

Brucehankins

Harvey wow, way more help than I was expecting! Thank you so much!

My goal is to package for myself to start, learning little by little, till one day hopefully I can contribute and help everyone else who's working so hard on this amazing project.