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

List:       kwrite-devel
Subject:    Re: Supporting the CMake file API in the project/build plugin ?
From:       christoph () cullmann ! io
Date:       2023-11-25 14:05:48
Message-ID: b85675f90beae795939b132c64c802ef () cullmann ! io
[Download RAW message or body]

On 2023-11-24 17:32, Alexander Neundorf wrote:
> On Freitag, 24. November 2023 10:45:23 CET christoph@cullmann.io wrote:
>> On 2023-11-23 23:31, Alexander Neundorf wrote:
>> > On Donnerstag, 23. November 2023 19:56:00 CET christoph@cullmann.io
>> >
>> > wrote:
>> >> On 2023-11-20 22:23, Alexander Neundorf wrote:
>> > ...
>> >
>> >> > If the user has opened a file in the source tree before, and git/svn
>> >> > auto projects are enabled, no cmake project will be created, i.e. no
>> >> > build commands.
>> >> > Should I add an explicit entry like "Open CMake build tree" or
>> >> > something like this in the project menu ?
>> >>
>> >> I would hope that 'open folder' works for that, I would rather not
>> >> have an extra entry that just do the same.
>> >
>> > I was not aware of that option and actually don't know when I should
>> > use it.
>> > What is it supposed to do ?
>> 
>> Hi,
>> 
>> it will tell the project plugin to open the folder as project and that
>> should trigger all the current active git/svn/.... auto detections and
>> if all fail open the stuff as plain 'recursive filesystem' project.
> 
> Thanks, I didn't know that.
> But I'm afraid it doesn't change a lot.
> To trigger the cmake file API stuff, a user will have to "open" the 
> build
> directory, which normally probably nobody will do.

Hi,

but that was the same before, I don't think an extra menu entry is that 
helpful beside
making the menu more crowded. One just needs to document that stuff and 
people will get
used to it, before one needs to go to the build dir manually, too.

Greetings
Christoph


> 
> Alex
[prev in list] [next in list] [prev in thread] [next in thread]