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

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

Hi,

Great! That is exactly what I need.
I see there is already some scanning done before the first build. I guess the default Toolchain selected in the launch configuration build settings is used to get some initial include paths. How can I change the core build project's default toolchain?

I see that the CMakeBuildConfiguration and StandardBuildConfiguration classes are responsible for building the core build cmake and makefile projects. I do not see yet how exactly the build output is captured, parsed, combined with toolchain information and sent to the scanner/indexer. Is there a core build design document?

regards,

-- 
Erwin Waterlander                                                 Intel

-----Original Message-----
From: cdt-dev <cdt-dev-bounces@xxxxxxxxxxx> On Behalf Of Martin Weber
Sent: Monday, October 03, 2022 13:35
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Managing include paths and macros in 'Core Build' projects.

Am Montag, 3. Oktober 2022, 12:57:20 CEST schrieb Waterlander, Erwin:
> -----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.
> > 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.
> Hi,
> 
> So this means that if I you run different C compilers, with their own 
> specific macros and includes, on different source files in a single 
> build from the same CMake file, you still get correct syntax 
> highlighting for all the source files. Right?

Yes.

/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.