How to work on KDevelop with KDevelop

[Benjamin Huth]

Thanks to both of you, Sven and Igor!

Actually I was unaware of the fact that the session each launch an own 
instance, I always thought that there is just an additional MainWindow 
created...

But that makes it all far more easy to setup now, especially with your 
pointers, Igor.

After having done this, I actually wonder if it wouldn't be nice to add 
this info e.g. to https://kdevelop.org/contribute-kdevelop/, because 
actually the information currently on the website is not super helpful 
with that... There is also only described the build with kdesrc-build, 
but it seems like that it is also quite common to just build against the 
system libraries (which I did as well, and which is simpler in my 
opinion...)

I would be willing to draft/rewrite these parts on the website, but I 
don't know how to get started with this...

Cheers,
Benjamin


On 24.02.24 08:40, Igor Kushnir wrote:
> Hi Benjamin,
>
> Sven has already answered your question. You may find the following
> KDevelop development workflow discussions useful too:
> https://mail.kde.org/pipermail/kdevelop-devel/2020-March/063470.html
> https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/490#note_766158
>
> Cheers,
> Igor
>
> On 2024-02-24 01:39, Sven Brauch wrote:
>> Hi,
>>
>> On 23.02.24 23:24, Benjamin Huth wrote:
>>> This I would like to do within KDevelop itself, however I'm not sure 
>>> what the best workflow is there. The issue is that I cannot launch 
>>> KDevelop from KDevelop, because it only allows a single instance 
>>> running for a given user, and always closing the development 
>>> instance to check changes in the freshly built one is a bit unpleasant.
>>
>> that's not true, you can create a new session and have 2 instances 
>> open with different sessions. See kdevelop --help, especially 
>> kdevelop -s and kdevelop --pick-session.
>>
>> Greetings,
>> Sven