Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Managing include paths and macros in 'Core Build' projects.
  • From: "Waterlander, Erwin" <erwin.waterlander@xxxxxxxxx>
  • Date: Tue, 27 Sep 2022 08:57:20 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=7fOoWWK4dev/67hEKCSNOIeWAXkB2+eQjPn/REQ+na4=; b=OP9H2CWZ7BahaSqvnUQ0nPl4WqtAcXXsy5+UWHSTuylNzpS/6ESBnXK1bMMOsIECwQRXL9DLi6H2kw5spPvMqetIdgOa3756UnP2fskUgdxpF4jT8cnQI0SLVqxpfE227QWOfS6+Jp/rkFwHQplI9jQrsh51Y1Zb6r/p7F5nyAdwOevqq86ZRMkn1xR80LChCUJ/8sVxplpVkdcJhPdvb8/BJq3DJZ7YjkBpgqZy1dujcIZROb2uOjNTmNWf+jmCFlV2c/ShL15VAi618dPDKeBMOhrGcYtA+nLbG2WIQfxqC50BSyHL5Skrp5I4qcYqVJF+Vot14Q6eEXYXMxeBIw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=ECu6t3pSSBNrAg/SoJTbXskeDimo7tTMtXoay2cYiHOa1nkyqMEKfPtDegJzUwRw8qA4YmDTAzLsYgvL5huSLexiqVc0BAJrdEztl5H5TA9BAYhVn4p0ie09PS6ZE3RvVk+Dfn9G0dq2ObeDJt2WGfUSexceK1Xhlabnon6a30rWXkew7li9yGg50CQj/9rnirHi+Fg+Aj6ChN2yJBDzDs/7WO1MpNnkojUAgl2xvNNmXgny/D+umbDoMR+JyfVN0s8S9eULvHNwxkUjbDATBYblBBP1J4Wr+0BJWxtczKEnIgzCbLgdnxsPWILYXJ2k9PaOa/jl5jSNYXA1mgbjsQ==
  • Delivered-to: cdt-dev@xxxxxxxxxxx
  • Dlp-product: dlpe-windows
  • Dlp-reaction: no-action
  • Dlp-version: 11.6.500.17
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: AdjNhqEfp/QsKTJySAqOeK9J3F55BAACWKqAADNe8BAABdjogAAoE3cgAAqVKgAADPOCAAC2dBIg
  • Thread-topic: [cdt-dev] Managing include paths and macros in 'Core Build' projects.

Thanks Martin, I have a look.
I do not see yet how I add a custom detection participant to my plugin. Which extension to use? I'm using Eclipse 4.23/CDT 10.6.
Is there any tutorial on how to create a CDT core build plugin, like there is for managed build?
I will also have a look at cmake4eclipse. I will send you a PM if needed.

best regards,

Erwin Waterlander                                                 Intel

-----Original Message-----
From: cdt-dev <cdt-dev-bounces@xxxxxxxxxxx> On Behalf Of Martin Weber
Sent: Friday, September 23, 2022 19:39
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Managing include paths and macros in 'Core Build' projects.

Am Freitag, 23. September 2022, 13:27:54 CEST schrieb Jonah Graham:
> Hi Erwin,

Hi Erwin,
> For discovering the built in include paths of any compiler (gcc isn't 
> overly special) CDT runs the compiler with special command line and 
> the compiler prints out on stdout the built in include paths.
> I haven't done this myself, so my instructions may be a bit off... If 
> your compiler doesn't behave like gcc, then the default command line 
> mentioned above may not work, use the extension point 
> org.eclipse.cdt.jsoncdb.core.detectionParticipant
> to configure that part. See
> soncdb
> .microsoft for an example.

Better look at <
org.eclipse.cdt.jsoncdb.nvidia>, it is a more elaborated example.
Gcc builtin detection is here <

Note that the extension point is used by CDT *cmake core build* as well as by my cmake4eclipse-plugin. The latter is to integrate cmake into CDT *managed build*.

If you have any question, send me a PM.


Cd wrttn wtht vwls s mch trsr.

cdt-dev mailing list
To unsubscribe from this list, visit
Intel Benelux B.V.
Registered in The Netherlands under number 24134020
Statutory seat: Rotterdam
Registered address: Capronilaan 37, 1119NG Schiphol-Rijk

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Back to the top