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

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

Thanks Erwin for the question.

My understanding matches Kondal's. 

It does leave open the question of how to present that to the user in a way that doesn't irritate them. Perhaps there should be a better way to inform the user than a warning lost under a sea of errors?

Also I seem to see a bug with Includes node simply missing, even though after the build the includes have resolved fine. Is this just my CDT dev environment gone wrong, or do other see this too?

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com

On Wed, 21 Sept 2022 at 03:59, Kondal Kolipaka <kondal.kolipaka@xxxxxxxxx> wrote:

AFAIK, there is no option to add include paths and macros for core CMake projects. Indexer is designed to get these details from the compiler_commands.json file after the build.

Best Regards,

Kondal Kolipaka

On Wed, Sep 21, 2022 at 12:34 PM Waterlander, Erwin <erwin.waterlander@xxxxxxxxx> wrote:

Hi,

In 'Managed Build' projects I can add my custom Language Provider to add include paths and macros needed for syntax high lighting and code navigation.

How is this supposed to be done in 'Core Build' projects, Cmake and Make projects?

Typically Core Build projects show no includes in the Project Explorer at start. Not even the gcc includes.
Make projects have only limited options to add include paths and macros. Variables are not supported as far as I see.
In CMake project properties I see no options for include paths and macros at all.

regards,

--
Erwin Waterlander                 Intel
The Netherlands

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

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev