IDE integration

Instead of building your application within Rhapsody, your application is build inside your IDE where all knowhow is available on target derivates, memory maps and even boards, simulator-, debugger- and emulator specifics. Your IDE may come with a Wizard and your tool manufactorer will have provided extensive documentation on how and where to tweak settings in the IDE to accomplish some setting.

In order to build your application in your IDE, the Rhapsody generated sources must be available inside an IDE project. You can either use a product or an adaptation which supports a Deployer to copy all generated files to an IDE project and also update the IDE project file so all your sources will show up in the IDE or integrate files in the IDE project manually. To prevent you from having to specify various constants which are used in the RXF or its Bridges, the Rhapsody build process will generate a few include files - one for configuring the size of queues for example, and another include file for defining constants used in the Bridges. What you must do yourselves is specify include paths and that you want to link with OO RTX and RXF libraries.

The Deployer is a separate application which is launched when you select Run in Rhapsody. You will use:

Code | Generate or Code | Regenerate to generate your application sources
Code | Build or Code | Rebuild to generate the necessary include files (with defined constants)
Code | Run to launch the Deployer

There will be some relation between your Rhapsody project and your IDE project: certain Rhapsody generated sources or packages must end up at dedicated folders in your IDE. At the same time, chances are that Rhapsody itself or the IDE project you are using is not installed or located at the very same directory on the PC you and your collegues are using, or there are differences between development, QA and production environments.
For this, we have splitted the information needed for the deployer (where to deploy the generated files to):


In Rhapsody we use Tags to specify relative paths within IDE project	The Deployer uses absolute paths to your IDE project.

The Deployer stores information in the registry of your PC: the Deployer will popup the Configuration Dialog above only once for your project. The next time you press Code | Run in Rhapsody, it will not ask path information but just deploy the generated files into your IDE project.

Obviously you may need to change settings for the Deployer, which is why you can launch the Deployer Configuration Dialog from the Rhapsody Tools menu. The Deployer stores information on the combination of Rhapsody project, the specified rootTitle and active component and environment versus the IDE project. If you change environment, select a different active component in your Rhapsody model, or open a different Rhapsody project, the Deployer Configuration Dialog pops up when you start deploying your generated files.

Please note that the environment includes the exact version number of your product: if you install a new version of your product (which can co-exist with your existing product), the Deployer Configuration Dialog pops up when you start deploying your generated files. This prevents you to use the new product (-version) with a the same IDE project by accident.

Please note: The IDE integration is not part of all products or adaptations.