A.1.2. Packaging the system model for distribution

If you are running the model in the same environment where the model was created, all DLLs and support files are already available to the model.

If, however, you are packaging the system model for use on a system that does not have Fast Models installed, you must include the required DLLs and support files as part of the package.

Note

When the model is built, the output files are placed in a deployment subdirectory in the directory that contains the source project file. By default the name of the deployment subdirectory matches the build options selected from the Select Active Project Configuration drop-down list on the System Canvas toolbar:

  • Win32-Debug-VC2005 is a debug version of the model built with VC2005.

  • Win32-Release-VC2005 is a release version of the model built with VC2005.

  • Win32-Debug-VC2008 is a debug version of the model built with VC2008.

  • Win32-Release-VC2008 is a release version of the model built with VC2008.

  • Linux-Release-GCC-3.4 is a version of the model built with version 3.4 of GCC.

  • Linux-Release-GCC-4.1 is a version of the model built with version 4.1 of GCC.

You can also create your own custom build configuration option. In this case, the name of the deployment directory matches the name of your custom build configuration.

For more information on deployment options for user-supplied files, see File/Path Properties dialog.

Packaging the model for use on Linux

The following steps must be followed if your model is to be used by others:

  • Ship any user-defined files such as text files or application files

  • Ship any shared libraries for custom components you created

  • Ship the following files from the deployment directory for the model you built:

    • libMAXCOREInitSimulationEngine.so.2

    • libarmctmodel.so

    • libSDL-1.2.so.0.11.2 (required if your model uses the PL041 AACI component or uses any visualization components).

  • If Ethernet components are used, ensure that the end user has libpcap installed.

Packaging the model for use on Windows

The following steps must be followed if your model is to be used by others:

  • Ship any user-defined files such as text files or application files

  • Ship any DLLs for custom components you created

  • Ship the following files from the deployment directory for the model you built:

    • libMAXCOREInitSimulationEngine.2.dll

    • SDL.dll (required if your model uses the PL041 AACI component or uses any visualization components)

    • armctmodel.dll

    • pktethernet.dll (if Ethernet components are used).

  • If Ethernet components are used, ensure that the end user has winpcap installed.

  • Ensure that the end user has one of the following applications installed:

    • a compatible version of Microsoft Visual Studio installed for running Debug builds (VC2005 SP1 or VC2008 SP1)

    • the Microsoft Visual Studio Redistributable Package (2005 SP1 or 2008 SP1) for Release builds.

Copyright © 2007-2010 ARM Limited. All rights reserved.ARM DUI 0370K
Non-ConfidentialID110210