Specifying compilation options with orcc_run_compilation

[robstewart57]

The wiki says:

<additional_flags> can be used to give other arguments to the back-end. This is not documented for now.

There are a number of options with the Xronos backend that I would like to enable in the following screenshot:

Specifically:

• Generate Go/Done Signal for each Action
• New LIM Generation (Beta)

How do I indicate those options to the orcc_run_compilation script?

[Junaiid-Ahmad]

Hi Rob,

I believe Xronos back-end is extending AbstractBackend.
To support new options for compiling a backend from the command line, these options can be added to the start(...) method of AbstractBackend.

Note that it would also require to define options like-optionKey for each option, to be used to specify options as -optoinKey optionValue on the command line.

I hope this helps.
Junaid

[robstewart57]

Hi Junaid,

Before I get that far, how do I include Xronos when setting up eclipse for headless builds. Currently the command is:

$SCRIPTS_DIR/orcc_eclipse_setup $WORK_DIR file:$ORCC_DIR/eclipse/plugins/net.sf.orcc.site/target/repository/

To include Xronos as an addition repository, what would the command be?

$SCRIPTS_DIR/orcc_eclipse_setup $WORK_DIR file:$ORCC_DIR/eclipse/plugins/net.sf.orcc.site/target/repository/,file:/path/to/xronos/eclipse/plugins/org.xronos.???

It is possible for the -repository option to the eclipse command to receive a comma separated list of repositories, see here: https://www.eclipse.org/forums/index.php/t/1079277/ .