The scope for each contains a class with statechart. Each statechart prints a simple message to standard output. 
 

Now lets build and run the projects:
 
i) Configure your target connection. See section 5.1 Configuring SSH for a remote target
and 5.2 Configuring a local docker container target for configuring targets. 

ii) Open the features window for the project and set the stereotype for your target connection. Select only one stereotype from TestPkg.

iii) Set the active component to either GCCSTATICLIB or CLANGSTATICLIB (depends on the target selected in previous step)

iv) Use Build Framework from the Code menu to compile the OXF on the target.

The OXF build process will proceed at the output window. This can take a few minutes, depending on network speeds.

v) Using the "Generate/Make/Run" toolbar button, build the three components for your target in turn.

For example, GCCSTATICLIB, GCCSHAREDLIB and GCCEXE.  Or CLANGSTATICLIB, CLANGSHAREDLIB and CLANGEXE.

In addition to the normal model checker and code generation messages, the output window now also shows additional messages:

• User Authentication based on the credentials added to the logins.txt file
• Connection status to the remote target
• Transfer of project source files to the remote target (including source/target filesystem locations)
• Build of project source files
• Transfer of binary files. DSO libraries are copied to /usr/local/lib automatically so they can be found during runtime. Executable binaries are copied back to the local host to enable the "Run" button in the Rhapsody code toolbar.
• Build summary. Runs "file" command on the finished binary file.
   

Since we have used the GMR button the executable component will automatically run after the build completes. It will open a terminal window, connect to the target and execute.


4.2 Creating a new project

Create a new C or C++ project as usual.
Use Add profile to model in the File menu to add the NativeTargetProfile to the project.





4.3 Adding a Library component 

• Add a component
• Set the Type to Library in the general tab
• Set the corresponding stereotype for the OS/toolchain/language
   

  Stereotype Name	Description
  DSHARED_CPP	Darwin/LLVM DSO lib for C++
  DSHARED_C	Darwin/LLVM DSO for C
  LSHARED_CPP	Linux/GNU DSO for C++
  LSHARED_C	Linux/GNU DSO for C
  DSTATIC_CPP	Darwin/LLVM static lib for C++
  DSTATIC_C	Darwin/LLVM static lib for C
  LSTATIC_CPP	Linux/GNU static lib for C++
  LSTATIC_C	Linux/GNU static lib for C

  
  For example:
  
  
   
• Add your model elements to the project as normal. 
• Select these model elements under the new component's Scope tab.
• Use the toolbar GMR button or the individual code > generate/make/run commands

    
4.4 Adding an executable component
 

• Add a component
• Set the Type to Executable in the general tab
• Set the corresponding stereotype for the OS/toolchain/language
   

  Stereotype Name	Description
  DEXE_CPP	Darwin/LLVM executable binary for C++
  DEXE_C	Darwin/LLVM executable binary for C
  LEXE_CPP	Linux/GNU executable binary for C++
  LEXE_C	Linux/GNU executable binary for C

•  Add your model elements to the project as normal. 
• Select these model elements under the new component's Scope tab.
• Use the toolbar GMR button or the indiviudal code > generate/make/run commands

5.1 Configuring SSH for a remote target

You will receive this message:
 


You must select YES or Rhapsody will be unable to connect.

iii) For security reasons your passwords will not be stored in the Rhapsody model. Instead login credentials are stored in the scripts\logins.txt file.



Note this format is compatible with Powershell hashtables. This code for this mechanism can be found in scripts\misc\common.ps1. 

• Add a new stereotype with a name describing your target. e.g. MacbookRemote or UbuntuDesktop
• Set the stereotype applicable to Component and Project.
• Add a generalization from the your stereotype to the NativeTargetProfile::remote stereotype.
   
  
  If you're using the example projects you can skip the above steps and use one of the stereotypes provided.
   
• Set the following properties:
   

  Property Name	Description
  NativeTarget::Configuration::RemoteTarget	This should be the IP address or FQDN of the remote target
  NativeTarget::Configuration::RemoteTargetUsername	This is the user name for the remote target account
  NativeTarget::Configuration::RemotePwdFile	This is the username/password file. It is located in the profile/scripts folder.

  
  For example:
  
   
   
• Apply your stereotype to the component.
   

• Add a new stereotype with a name describing your docker target. e.g. DockerUbuntu 
• Set the stereotype applicable to Component and Project.
• Add a generalization from the your stereotype to the NativeTargetProfile::virtual stereotype.
• Set the properties:

• Apply your stereotype to the component.

5.3 Location for source code and binaries.
 

• Project code is copied to the following locations on the target

  • For Darwin: /Users/<Username>/rhp_workspace

  • For Linux: /root/rhp_workspace or /home/<Username>/rhp_workspace

  • <Username> is set by the NativeTarget::Configuration::RemoteTargetUsername property. If you set "root" as the username for Linux targets the alternative path will be used. See "Setting the login credentials for your target" section.

• Project binaries are built in the component/configuration path as per usual Rhapsody behavior.

  • OXF code is copied and built at the rhp_workspace/Share location for both Darwin and Linux.

  • DSO libraries are copied to /usr/local/lib to allow easy access during runtime. Note that the C and C++ OXF DSO libraries have the same name so  will overwrite each other. Therefore, you must rebuild the OXF when switching between C and C++ projects.

  • The "rhp_workspace" default can be changed by modifying the $rhpWorkspace variable in all three powershel scripts located in the \scripts\ssh\ folder of the profile.

• CPP_CG::NativeTarget::UseOXFDSO

    
5.7. Modifying executable binary component settings
 

5.8. Modifying the OXF Framework


The OXF source files for Linux and Darwin can be found in the env\Linux and env\Darwin folders of the profile. The files are archived as Share.tar files. These archive files are copied over to the remote target, before being unpacked and rebuilt. Therefore, to make changes to these source files you must first unpack them locally to make changes, then re-pack them before using Build Framework from the Code menu. Please ensure that you save source files with Unix-like EOL conversions. It is recommended to use 7zip to create the tar file and that the PathMode option is set to "Full Pathnames".

    
5.9. Modifying the Build Framework, Invoke Make and Invoke Run toolbar operations


The toolbar button functionality is defined by the following properties defined in properties\NativeTargetProfile.prp:
 

Powershell scripts are located in the scripts folder of the profile directory. Rhapsody properties are sent to the scripts as parameters.