Building kate as documented on the web page

[Dominik Haumann]

Hi Alex!

https://invent.kde.org/websites/kate-editor-org
This is Kate's website.

The reason why we suggest kdesrc-build is because if you compile Kate, you
likely also need KTextEditor and KSyntaxHighlighting. And the frameworks
cannot be built standalone, since also ecm is typically checked to make
sure all frameworks have the same version.

To avoid user questions all over the time about half baked kate compiles,
kdesrc-build is the only correct answer.

PS: I know that for you it's easy to use cmake directly. But with your
cmake background, you are pretty much above average as much as one could be.

Best regards
Dominik

Alexander Neundorf <neundorf at kde.org> schrieb am Mi., 2. Feb. 2022, 21:33:

> On Mittwoch, 2. Februar 2022 11:11:40 CET Christoph Cullmann (cullmann.io)
>
> wrote:
> > On 2022-02-02 08:50, slbtty wrote:
> > > I think rolling-distro users like us are actually the minority.
> > >
> > > Stable-distro users don't have new libraries. If they ever want to
> > > build from source, they are highly going to manipulate the code. If
> > > so, letting them get sources from the master branch can avoid dealing
> > > with already fixed bugs in dependencies.
> >
> > Hi,
> >
> > I think if you have a distro that up-to-date that you can do that, you
> > don't need any howto.
> >
> > Without kdesrc-build you can't build it on any normal distro that is not
> > rolling release
> > that is not bleeding edge.
> >
> > Beside, if you want to work on other parts, a kdesrc-build setup is nice
> > to have
> > and it will properly setup the stuff for clangd if used like described.
> >
> > If you want to add to the howto the cmake variant, feel free to submit
> > some merge request
>
> stupid question: how/where would I create that merge request ?
>
> Alex
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kwrite-devel/attachments/20220202/0282b77c/attachment-0001.htm>