Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
lock attach
Attachments are accessible only for community members.
Not applicable
Dear support engineer,

in a DAVE project, i want to use the Compiler command options as a parameter for a prebuild command batch script.

This should look like:

...\buildsteps.bat ${FLAGS}

Unfortunately the ${FLAGS} variable is always empty.

Is there a way to access the compiler options at the the pre-builkd step stage?

Or am i doing something wrong?

The attached pictures further emphazise the problem.

Thanks and best regards

Felix

0 Likes
2 Replies
Not applicable
is the flag defined? is the flag used in the .bat file?
0 Likes
Not applicable
Hello shenj,

what i actually need for my .bat script are the command options for the gcc c compiler (see screenshot2 marked in blue).

In my prebuild commands i need to call the batch script as:

..\buildsteps.bat 0 "${ARM_GCC_HOME}" "${BuildArtifactFileBaseName}" "${needed_gcc_c_compiler_optionsstringvariable}" PLECS_PIL_SEPARATOR $(C_SRCS)

The variables "${ARM_GCC_HOME}" and $(C_SRCS) work fine here and already contain the information related to it.

From the command line pattern shown in screenshot2 i assumed that

${needed_gcc_c_compiler_optionsstringvariable} = ${FLAGS}

But unfortunately this variable is always empty, at least when the prebuild commands are evaluated.

So what i need is a variable that provides access to the gcc c compiler options, or at least the files/folders included "-I pathtoafolder -I..."?

I hope this clarifies the problem.

Thanks for your help.

Best Regards

Felix
0 Likes