Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Orgad Shaneh <orgads@gmail.com>
To: Nikolai Kosjar <nikolai.kosjar@qt.io>
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, 30 Nov 2016 10:43:55 +0200	[thread overview]
Message-ID: <CAGHpTBLc8Hw1kYmKX0Z1PCH5pNSd8t=jMN1h4TE1dMEy5+bNDA@mail.gmail.com> (raw)
In-Reply-To: <736bee70-7a99-8681-a976-f6fdb4e524a0@qt.io>

On Tue, Nov 29, 2016 at 10:55 AM, Nikolai Kosjar <nikolai.kosjar@qt.io> wrote:
> On 11/28/2016 07:03 PM, Jason A. Donenfeld wrote:
>>
>> On Wed, Nov 23, 2016 at 8:45 AM, Konstantin Tokarev <annulen@yandex.ru>
>> 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 the Clang Code Model, Qt Creator from the current 4.2
> branch.
>
> The corresponding report was
> https://bugreports.qt.io/browse/QTCREATORBUG-15590.

It should also work with the built-in code model. Not sure why Jason
claimed it doesn't. Did you try it?

- Orgad

  parent reply	other threads:[~2016-11-30  8:39 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 [this message]
2016-11-29  8:56   ` Nikolai Kosjar
2016-11-23  7:58 ` Orgad Shaneh
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='CAGHpTBLc8Hw1kYmKX0Z1PCH5pNSd8t=jMN1h4TE1dMEy5+bNDA@mail.gmail.com' \
    --to=orgads@gmail.com \
    --cc=nikolai.kosjar@qt.io \
    --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).