Create RXF Library

RXF

It is a good idea to use a library for the RXF including the embOS adapter, which you can link with your application. This will decrease its footprint, because unused functions will not be allocated by your linker. Our example GettingStarted also relies on using libraries for the RXF, and support the two buildsets Debug and Release.

Due to Known Issue #1356 regarding the C keyword const and assuming it refers to ROM, we implemented a workaround using the AWK script RemoveConstKeyword.awk This script is used during installation of the product so the RXF sources are processed, in the examples and in each and every Rhapsody project before deploying your sources. The result of the script is always captured in a subdirectory Workaround.

If you specify that constant data is located in far memory, then you must use the keyword __far when accessing such data.

We provided a complete Embedded Workbench workspace and the project CreateRXFLibrary to build your libraries, which match the Blinky example. The CreateRXFLibrary Project Workspace is installed in <your Rhapsody>\Share\WST_RXF_V5\<your product>\Samples\Code\Workaround\CreateRXFLibrary which Project Workspace you can open in Embedded Workbench:

If you need a different derivate, data model or location for constant data, you can modify the settings in the projects included in the project as described on the section how to change derivate, but please do so after the demo.

Build the libraries using Project | Rebuild all. We already inserted references to the C sources and include files of the RXF which are installed in <your Rhapsody>\Share\WST_RXF_V5\<your product>\Source and the embOS RTOS:

Make the other project active, and rebuild that library too:

You can inspect the settings for each configuration in the Embedded Workbench project:

You will notice that only a few things are set:

for the General Options, on the Output Tab we specified that a library must be created
for the C/C++ Compiler, a macro _DEBUG (RXFD) or NDEBUG (RXFR) which enables the proper C code in RxfConstants.h
for the C/C++ Compiler, relative include paths to <your Rhapsody>\Share\WST_RXF_V5\<your product>\Source\Workaround and embOS
for the C/C++ Compiler, in the RXFD Target, on the Output Tab the checkbox 'Debug information' is enabled.
for the Library Builder, the Output Tab specifies that we override the default and we specified that the library must be created in the directory in <your Rhapsody>\Share\WST_RXF_V5\<your product>\Source\Lib\Workaround

The two project configurations Debug and Release result in the libraries RXFD.r34 and RXFR.r34

NOTE

The options or constants set via CppCompileSwitches in your Buildsets must match the options in your Embedded Workbench project CreateRXFLibrary to create RXF libraries. You should not compile the libraries with for example support for UML ports, or use highwatermarks in a debug version, and use different options to compile your application with.

If you need a different derivate, you can modify the settings on the Target Tab in for both EW project configurations Debug and Release. You also may need to change the Target and RTOS Bridge included in your product as described on the section how to change derivate, but please do so after the demo.