cancel
Showing results for 
Search instead for 
Did you mean: 

SPC5Studio-6.0.0-Clarke CDT

PChia.2237
Senior

Hi,

there is possibility that ST fix Build Output Parser (BOP) to have confortable IDE.

Okay i can add :

C:\SPC5Studio-6.0\eclipse\plugins\com.st.tools.spc5.tools.gnu.gcc.ppcvle.win32_4.9.4.20200908161514\toolchain\include

C:\SPC5Studio-6.0\eclipse\plugins\com.st.tools.spc5.tools.gnu.gcc.ppcvle.win32_4.9.4.20200908161514\toolchain\lib\gcc\powerpc-eabivle\4.9.4\include

it fix only standar library.

I have external folder "custom" with file analog.c :

static adcsample_t AnBuffer[ADC0_GROUP_ANALOG_INPUT_NUM_CHANNELS *

  ADC0_GROUP_ANALOG_INPUT_BUF_DEPTH];

ADC0_GROUP_ANALOG_INPUT_NUM_CHANNELS and ADC0_GROUP_ANALOG_INPUT_BUF_DEPTH

are not recognized and still mark like not resolved.

Description Resource Path Location Type

Symbol 'ADC0_GROUP_ANALOG_INPUT_NUM_CHANNELS' could not be resolved analog.c /EcuFullBrigeBase/custom line 10 Semantic Error

Build works good, but preprocesser, indexer not.

Please how can i works without CDT preprocessor errors?

I see in Eclipes CDT:

  1. Build Output Parser (BOP). Another method that CDT employs is to analyze build output of the regular build with Build Output Parser. Often, include paths are supplied to the compiler with -I options, and macros with -D options and BOP will try to find those in the output. That method relies on verbose build output of your build where all these options are actually printed by make.

But if i enable :

CDT GCC Build Ouput Parser

CDT GCC Built-in Compiler Settings

not works and i have others error.

Thank you and advantages!

This discussion has been locked for participation. If you have a question, please start a new topic in order to ask your question
0 REPLIES 0