feat(desktop/appimage): use KDE Craft and their binary cache to get Qt - #877
Conversation
eacf2b9 to
92d5067
Compare
|
we also need a way to build the cache itself to be uploaded on our download server |
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
ensure proper search path for pkgconf by setting PKG_CONFIG_PATH env variable before calls to craft will enable the build to find libraries provided by the host system Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
f37cc0b to
24982c2
Compare
partilally rely on KDE binary cache for Craft enforce using Qt 6.9.3 for our stable branch Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
0133664 to
662725e
Compare
b93e619 to
7ede9aa
Compare
we have one image to build all dependencies: manual steps needed to get them into an archive one image to build the client with dependencies already there as binaries Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
switch to using Debian forky to get newer dependencies Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
7ede9aa to
8f756b7
Compare
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
8b9217b to
5a3a1ac
Compare
| RUN \ | ||
| wget https://download.nextcloud.com/desktop/development/qt/${CRAFT_IMAGE} && \ | ||
| tar xf ${CRAFT_IMAGE} && \ | ||
| rm ${CRAFT_IMAGE} \ | ||
| ; |
There was a problem hiding this comment.
Would it be possible to use the image from the Dockerfile.build.el8 as the base of this container? that way we wouldn't need to manually create/download+unpack an archive of the Craft installation, and we could also skip setting up the blueprint repositories here.
There was a problem hiding this comment.
we currently manually build Qt6 modules while building the first image
this is taking a lot of storage space and build time
I think the current limit when building an image would be exceeded
that is the main reason to keep a manual build step on some developer machine before using the actions to publish the final image
No description provided.