From kwrite-devel Wed Feb 02 21:06:35 2022 From: Dominik Haumann Date: Wed, 02 Feb 2022 21:06:35 +0000 To: kwrite-devel Subject: Re: Building kate as documented on the web page Message-Id: X-MARC-Message: https://marc.info/?l=kwrite-devel&m=164383589821251 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--0000000000003fe5c905d70f65e8" --0000000000003fe5c905d70f65e8 Content-Type: text/plain; charset="UTF-8" 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 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 > > > > --0000000000003fe5c905d70f65e8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Alex!

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

T= he reason why we suggest kdesrc-build is because if you compile Kate, you l= ikely also need KTextEditor and KSyntaxHighlighting. And the frameworks can= not be built standalone, since also ecm is typically checked to make sure a= ll frameworks have the same version.

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

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

Best regards
Dominik

Alexander Neun= dorf <neundorf@kde.org> schri= eb am Mi., 2. Feb. 2022, 21:33:
On = Mittwoch, 2. Februar 2022 11:11:40 CET Christoph Cullmann (cullmann.io<= /a>)
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 wa= nt to
> > build from source, they are highly going to manipulate the code. = If
> > so, letting them get sources from the master branch can avoid dea= ling
> > 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 ni= ce
> 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



--0000000000003fe5c905d70f65e8--