On Tue, Nov 29, 2016 at 10:55 AM, Nikolai Kosjar wrote:
> On 11/28/2016 07:03 PM, Jason A. Donenfeld wrote:
>>
>> On Wed, Nov 23, 2016 at 8:45 AM, Konstantin Tokarev
>> wrote:
>>>
>>> You can set PRECOMPILED_HEADER = header.h in your pro file. It should
Hi Nikolai,
On Tue, Nov 29, 2016 at 9:55 AM, Nikolai Kosjar wrote:
> Should work with the Clang Code Model, Qt Creator from the current 4.2
> branch.
>
> The corresponding report was
> https://bugreports.qt.io/browse/QTCREATORBUG-15590.
Okay, in that case, I'll wait until
Hi Marco,
I'll start compiling a list for you, so that I can give you something
more useful than my last message. For starters, here's one bug found
within seconds:
1. Open a file in the project. All seems fine.
2. Ctrl click on a function that points to somewhere in the Linux
kernel headers.
3.
On 11/23/2016 08:45 AM, Konstantin Tokarev wrote:
23.11.2016, 08:51, "Jason A. Donenfeld" :
Hello Eike & Qt Creator mailing list,
I'm insane and decided to try using an IDE for Linux kernel
development. Much to my delight, it actually works well. (Everybody on
the mailing list
On 11/28/2016 07:03 PM, Jason A. Donenfeld wrote:
On Wed, Nov 23, 2016 at 8:45 AM, Konstantin Tokarev wrote:
You can set PRECOMPILED_HEADER = header.h in your pro file. It should be
applied to all sources.
Nope, that's certainly not what that field does.
Should work with
On Mon, Nov 28, 2016 at 07:03:39PM +0100, Jason A. Donenfeld wrote:
> Hello All,
>
> Responses to each of you are inline below.
>
> Sounds to me like there's a lot of work to be done, still, and I
> haven't received any enthusiastic responses from the Qt team of, "yes!
> we'd love to work on
Hello All,
Responses to each of you are inline below.
Sounds to me like there's a lot of work to be done, still, and I
haven't received any enthusiastic responses from the Qt team of, "yes!
we'd love to work on this and make Qt Creator suitable for kernel
development!" Bummer. Seems like a great
ery file of the project. This
> is a major hindrance. It means that every ifdef for every kconfig
> option is a grayed out unclickable region, rendering most things
> useless. Developers: any interest in fixing this? I spoke to a few of
> you in IRC several months ago about this, and there was
perly.
> Developers: any interest in fixing this? I spoke to a few of
> you in IRC several months ago about this, and there was interest, but
> it seems to have evaporated.
>
> So, anyway, if you think it would be cool to be able to say, "Qt
> Creator is used for Linux Kernel