-
Notifications
You must be signed in to change notification settings - Fork 37
feat(desktop/appimage): use KDE Craft and their binary cache to get Qt #877
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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 <[email protected]>
Signed-off-by: Matthieu Gallien <[email protected]>
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 <[email protected]>
Signed-off-by: Matthieu Gallien <[email protected]>
Signed-off-by: Matthieu Gallien <[email protected]>
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 <[email protected]>
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 <[email protected]>
switch to using Debian forky to get newer dependencies Signed-off-by: Matthieu Gallien <[email protected]>
7ede9aa to
8f756b7
Compare
Signed-off-by: Matthieu Gallien <[email protected]>
Signed-off-by: Matthieu Gallien <[email protected]>
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.