During the load module packaging portion of construction, EABs are included in load modules just as other procedure steps and action blocks are included. When generation occurs for that load module, information identifying the action block is included in the generated ICM. However, the action block stub is not included in the resulting remote file. It must be moved to your target system as a separate file.
On the development platform, the EAB code must be moved from the source code component subdirectory (\c) associated with the model being implemented to the target system. The file containing EAB code is named using the action block name and a file extension appropriate to the language being used (.C).
When you move the action block to the target system, store it in any directory until the code is compiled. After compile, store the EABs in the file to which LOC.EXTERNAL_LIB Build Tool script token points. This is most likely a shared or archived library. The file LOC.EXTERNAL_LIB identifies is used during the load module link to add the EABs to the load module executable.
Note: For more information about the LOC.EXTERNAL_LIB token, see the Build Tool User Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|