[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kstars-devel
Subject:    Re: Binary Factory Mac Build Status
From:       Ingo =?ISO-8859-1?Q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2024-02-01 7:39:14
Message-ID: 4869511.GXAFRqVoOG () daneel
[Download RAW message or body]


On Donnerstag, 1. Februar 2024 05:52:54 CET Jasem Mutlaq wrote:
> Thank you Ingo,
> 
> That's a very helpful start.
> 
> So using a *single* craft.ini file,

.craft.ini with a leading dot.

> we can build KStars for MacOS & Windows
> on the same files? They do not have the same dependencies.

It will work as good or as bad as on Binary Factory. It's exactly the same 
Craft commands and blueprints that are used. The only difference is that for 
Binary Factory a few special options were made in a file called enabled-
projects.yaml. This is now done with the .craft.ini.

In theory, you could even overwrite many aspects of our standard Craft jobs on 
GitLab in your project's .gitlab-ci.yml, but then you are on your own.

> The current kstars.py

That should work as before on Binary Factory.

I just saw that you posted to the #kde-craft:kde.org Matrix room. That's good. 
Let's continue there.

Regards,
Ingo

> On Thu, Jan 25, 2024 at 8:04 PM Ingo Klöcker <kloecker@kde.org> wrote:
> > On Donnerstag, 25. Januar 2024 06:06:32 CET Jasem Mutlaq wrote:
> > > Thank you, are there any scripts that were made for complex KDE
> > > projects?
> > > That would be a great way to start and customize accordingly since none
> > 
> > of
> > 
> > > us have experience with this.
> > 
> > The builds are done with Craft pretty much the same way as they were done
> > on
> > Binary Factory.
> > 
> > The following .craft.ini file added to the root of kstars in the master
> > branch
> > should take care of indiserver:
> > ```
> > # SPDX-FileCopyrightText: None
> > # SPDX-License-Identifier: CC0-1.0
> > 
> > [BlueprintSettings]
> > libs/indiserver.version=master
> > libs/indiserver-3rdparty.version=master
> > libs/indiserver-3rdparty-libraries.version=master
> > ```
> > 
> > For your release branch, use the following .craft.ini to trigger a rebuild
> > of
> > indiserver and to enable building of an APPX package for Windows:
> > ```
> > # SPDX-FileCopyrightText: None
> > # SPDX-License-Identifier: CC0-1.0
> > 
> > [BlueprintSettings]
> > libs/indiserver.patchLevel=1
> > libs/indiserver-3rdparty.patchLevel=1
> > libs/indiserver-3rdparty-libraries.patchLevel=1
> > 
> > kde/applications/kstars.packageAppx = True
> > ```
> > 
> > If you have further questions then come to the Matrix room #kde-craft:
> > kde.org.
> > 
> > Regards,
> > Ingo
> > 
> > > On Wed, Jan 24, 2024 at 3:02 PM Ingo Klöcker <kloecker@kde.org> wrote:
> > > > Hi Jasem,
> > > > 
> > > > On Mittwoch, 24. Januar 2024 11:31:03 CET Jasem Mutlaq wrote:
> > > > > Thank you. Is there any documentation / guide on how to do this?
> > > > > That
> > > > 
> > > > would
> > > > 
> > > > > be greatly appreciated.
> > > > 
> > > > Although this blog talks about building Android APKs pretty much the
> > 
> > same
> > 
> > > > applies to any other builds that were previously done on Binary
> > 
> > Factory,
> > 
> > > > i.e.
> > > > you add some GitLab job template(s) to your .gitlab-ci.yml and maybe
> > 
> > add
> > 
> > > > some
> > > > settings for Craft to a .craft.ini file:
> > > > https://blogs.kde.org/2023/11/13/apks-now-built-invent
> > > > 
> > > > See
> > 
> > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/gitlab-template
> > 
> > > > s/ README.md
> > > > for a list of all GitLab job template(s).
> > > > 
> > > > Additionally, have a look at
> > 
> > https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/signing/README.
> > 
> > > > md which explains how to enable the different signing/publishing
> > 
> > services
> > 
> > > > used on
> > > > invent for KStars.
> > > > 
> > > > Regards,
> > > > Ingo
> > > > 
> > > > > On Wed, Jan 24, 2024 at 12:35 PM Ben Cooksley <bcooksley@kde.org>
> > 
> > wrote:
> > > > > > On Wed, Jan 24, 2024 at 9:00 PM Jasem Mutlaq <
> > 
> > mutlaqja@ikarustech.com>
> > 
> > > > > > wrote:
> > > > > >> Hello all,
> > > > > > 
> > > > > > Hey Jasem,
> > > > > > 
> > > > > >> Next version of KStars is due in a week. We can still see that
> > > > > >> the
> > > > > >> Mac
> > > > > >> Builder is down and we are wondering how we are going to release
> > 
> > it
> > 
> > > > for
> > > > 
> > > > > >> MacOS since there is no update or ETA on when this issue would be
> > > > > >> resolved.
> > > > > >> 
> > > > > >> The build process for KStars on MacOS is complex because it
> > 
> > involves
> > 
> > > > > >> building and distributing the INDI server and all 3rd party
> > 
> > drivers
> > 
> > > > along
> > > > 
> > > > > >> with it in addition to stellarsolver and other dependencies. But
> > 
> > it
> > 
> > > > has
> > > > 
> > > > > >> been working fine over the past few months without any issues
> > 
> > until
> > 
> > > > the
> > > > 
> > > > > >> Mac
> > > > > >> Builder failed recently.
> > > > > > 
> > > > > > As has been commented on Matrix several times - you need to port
> > > > > > to
> > > > > > the
> > > > > > Gitlab jobs provided in sysadmin/ci-utilities for this, the Binary
> > > > 
> > > > Factory
> > > > 
> > > > > > will soon be completely deprecated and shutdown.
> > > > > > These builds have the additional advantage of being available for
> > 
> > the
> > 
> > > > > > M
> > > > > > series processors Apple is using in their newer devices as well.
> > > > > > 
> > > > > >> --
> > > > > >> Best Regards,
> > > > > >> Jasem Mutlaq
> > > > > > 
> > > > > > Cheers,
> > > > > > Ben


["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]