[KDE/Mac] Compile & App Bundle Creation

[René J.V. Bertin]

On Wednesday June 15 2016 10:10:10 Christoph Cullmann wrote:

>Given that howto requires to compile for 20-30 minutes on my Mac up to Kate,
>I see no real time constraint to just paste the 20 lines of commands and let it
>run in the background to see if it works, but ok.

20 minutes to build *all* frameworks and Kate? I think that KIO alone takes about that time to build on my Mac (which isn't exactly slow despite going on 5yo). Maybe you didn't realise I do not have "stock" builds of the frameworks lying around, only builds that use my patched QStandardPaths configured for XDG-compliant locations?

>Given at the moment KDE software on Mac reaches close to nobody and most things just
>kind of work a bit, I see no point in spending any time on getting
>stuff to be shared between non existing applications.

That's a chicken-and-egg thing. There might be more incentive to build applications if there were a good installer for "stock" frameworks that can be used from a central location, from which they could then be embedded into a true standalone application in a 2nd step.

>And thats what this (badly written and incomplete) guide is for: help application maintainers
>(and contributors) to get a bundle of their application without a lot of hassle build.

Exactly what I'm saying :)

KDE has been conceived from and for a context where resources and libraries are shared from a central location. Staying as close as possible to that in a porting effort allows to focus and concentrate on the truly different things rather than spend lots of time figuring out infrastructure and logistics issues for each and every individual application. I remain convinced that this is the best (and most efficient) way to get to the highest possible quality applications. For example, some feature that cannot be made to work properly in an as-similar-as-possible context is unlikely to function properly in a standalone app bundle. So it's probably of little use to spend time on solving its infrastructure issues before finding out it doesn't work properly. Looking at it differently: if some feature doesn't work properly *after* doing the standalone app bundle dance means you have an additional potential reason for the dysfunction that you'll have to investigate.

R.