From: Orgad Shaneh <orgads@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
"qt-creator@qt-project.org" <qt-creator@qt-project.org>
Subject: Re: [Qt-creator] Qt Creator for Linux Kernel Development
Date: Wed, 23 Nov 2016 09:58:26 +0200 [thread overview]
Message-ID: <CAGHpTBJPXR08EMaHLtEawuQHRHOUF8MXsv1i_Kp_XTsWacdKqw@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qHaQDuFW+HNZFip-Ba7q3aXoCpHUNz06hnFezGwXbjug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1429 bytes --]
On Wed, Nov 23, 2016 at 7:51 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> (A) Qt Creator doesn't seem to parse the C correctly. Things like
> designated initializers and a few other C features here and there just
> don't get parsed correctly, and the IDE stops being useful. I suspect
> this is because things are actually being parsed in C++ mode. Bummer.
> Developers: any interest in improving C support in Qt Creator?
>
Which version do you use? Designated initializers support was added in 3.2 (
c56b999ffff249d4cb7dc7e8026a3297b63ff56d).
I now see that the members are not detected correctly (for e.g. Find
Usages), but parsing looks ok.
(B) There is no way to tell Qt Creator that a particular header file
> is included in every file -- that is, that gcc's "-include" is in use.
> There is a way of messing with the "C++ Code Model" on a file-by-file
> basis, for the duration of the time that the file is open, but no way
> to automatically have it included in every 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 interest, but
> it seems to have evaporated.
>
You can set PRECOMPILED_HEADER = header.h in your pro file. It should be
applied to all sources.
- Orgad
[-- Attachment #2: Type: text/html, Size: 2062 bytes --]
next prev parent reply other threads:[~2016-11-23 7:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 5:51 Jason A. Donenfeld
2016-11-23 7:45 ` [Qt-creator] " Konstantin Tokarev
2016-11-28 18:03 ` Jason A. Donenfeld
2016-11-28 19:49 ` Marco Bubke
2016-11-29 19:21 ` Jason A. Donenfeld
2016-11-28 21:34 ` André Pönitz
2016-11-29 8:55 ` Nikolai Kosjar
2016-11-29 19:23 ` Jason A. Donenfeld
2016-11-30 8:41 ` Nikolai Kosjar
2016-11-30 8:43 ` Orgad Shaneh
2016-11-29 8:56 ` Nikolai Kosjar
2016-11-23 7:58 ` Orgad Shaneh [this message]
2016-11-23 9:21 ` Eike Ziller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGHpTBJPXR08EMaHLtEawuQHRHOUF8MXsv1i_Kp_XTsWacdKqw@mail.gmail.com \
--to=orgads@gmail.com \
--cc=Jason@zx2c4.com \
--cc=qt-creator@qt-project.org \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).