Building kitinerary in the PIM docker

[Sandro Knauß]

Hey,

as the kdepim docker is based on Neon, that is based on Debian.
There are different things you can do to fix it. As Neon build the master 
branch you can check Neon, if a package is building successfully:
https://build.neon.kde.org/job/focal_unstable_kde_kitinerary_bin_amd64/

than you are able to run:
apt update
apt build-dep kitinerary

and this will list and install all dependencies needed to build the package. 
Keep in mind it will also try to install other kdepim dependencies. But it is 
great to look up a specific package name.

Another way is to look at the control file (Build-Depends):
https://invent.kde.org/neon/kde/kitinerary/-/blob/Neon/unstable/debian/control

And than the Debian KDE Packaging team also are confronted very often with 
these questions, so we automated it by creating a YAML file (by hand) to look 
up CMake Target and their corresponding Debian packages:
https://salsa.debian.org/qt-kde-team/pkg-kde-jenkins
-> hooks/prepare/cmake_deps.yml

used by
-> hooks/prepare/cmake_update_deps

[salsa is currently not available, that's why I cannot give you the concrete 
links]

(QMLPrivate is not listed so it does not help in this case). But we are happy 
if this file gets updates etc. via MRs ;)

Regards

hefee


On Montag, 28. Februar 2022 17:28:19 CET Volker Krause wrote:
> On Montag, 28. Februar 2022 13:48:04 CET Ingo Klöcker wrote:
> > On Montag, 28. Februar 2022 05:25:49 CET Glen Ditchfield wrote:
> > > I'm trying to build kitinerary master with the PIM docker image, but the
> > > build fails.  The error.log file ends with this:
> > > ===========
> > > -- Configuring done
> > > 
> > > CMake Error at src/lib/CMakeLists.txt:7 (add_library):
> > >   Target "KPimItinerary" links to target "Qt5::QmlPrivate" but the
> > > 
> > > target was
> > > 
> > >   not found.  Perhaps a find_package() call is missing for an IMPORTED
> > >   target, or an ALIAS target is missing?
> > > 
> > > ===========
> > > 
> > > What's missing?
> > 
> > The private headers of Qt QML are missing in the image. You can install
> > them in the running Docker container. (I cannot tell you how because I
> > don't know what distribution the image is based on.) The downside is that
> > anything you install in a running Docker container is lost as soon as the
> > container exits (unless you do some trickery with mounting a local
> > directory).
> 
> That would be my understanding as well, OTOH I do see
> "qtdeclarative5-private- dev" listed in
> https://invent.kde.org/pim/kdepim-docker/-/blob/master/ Dockerfile, which
> sounds like exactly that package...
> 
> Regards,
> Volker