Re: [cdt-dev] Managing include paths and macros in 'Core Build' projects

["Waterlander, Erwin" <erwin.waterlander@xxxxxxxxx>]

Hi,

My Eclipse installation was corrupted. After re-installing it I could see the detectionParticipant extension point (in 10.6). I'm able to make my own now. Thanks for all the help!

I'm also still very much interested in core build Makefile. If anyone has some hints how I could do the same for core build Makefile, I would appreciate it a lot. I like the simplicity of core build projects. Otherwise I have to stick to managed build Makefile.

kind regards,

-- 
Erwin Waterlander                                                 Intel

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

Am Dienstag, 27. September 2022, 10:57:20 CEST schrieb Waterlander, Erwin:
> 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

The extension point is 'org.eclipse.cdt.jsoncdb.core.detectionParticipant'. 
Not quite sure if it is present in CDT 10.6.

Just to clarify: What Jonah was suggesting is to build using the CDT CMake core project type and teach cmake core to handle your compiler (through the extension point). CDT CMake core has a mechanism to parse the compile_commands.json file and to pass the include paths and macros to the indexer.
The mechanism first isolates the name of compiler executable  from each commandline and then determines which of the existing detection participants feel responsible to capture the remaining arguments.
After parsing the command lines, the detections participant for each line is asked to supply the compiler built-ins for macros and include paths. Usually, the participant will invoke the compiler with special arguments to dump its builtins to stdout, parse that output and supply the builtins.

> tutorial on how to create a CDT core build plugin, like there is for

Not that I am aware of it.

> managed build? I will also have a look at cmake4eclipse. I will send 
> you a

cmake4eclipse uses the same mechanism as above to feed the indexer. The only difference is that is based on *managed build*.

 /Martin


--
Cd wrttn wtht vwls s mch trsr.




_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev
---------------------------------------------------------------------
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.