Attachments are accessible only for community members.
Not applicable
Jun 10, 2016
01:39 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 10, 2016
01:39 AM
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
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
- Tags:
- IFX
2 Replies
Not applicable
Jun 22, 2016
01:19 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 22, 2016
01:19 PM
is the flag defined? is the flag used in the .bat file?
Not applicable
Jul 21, 2016
05:06 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jul 21, 2016
05:06 AM
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
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