5.2.5 Header files and libraries for Microsoft Windows export

This section describes additional header files and libraries for SystemC export. Some are for build time, and others are for building and packaging the final virtual platform.

Header files and libraries to build the EVS on Microsoft Windows

The EVS requires specific header files and libraries.

  • Fast Models header files from %PVLIB_HOME%/include/fmruntime.
  • SystemC header files from %SYSTEMC_HOME%/include.
  • TLM header files from %TLM_HOME%/include/tlm.
  • AMBA-PV header files from %MAXCORE_HOME%/AMBA-PV/include if AMBA-PV ports are used.
  • %PVLIB_HOME%/lib/Winx_VCy/BuildType/fmruntime.lib, where x = 32, 64; y = 2008, 2010; BuildType = Debug, Release.
  • %PVLIB_HOME%/lib/Winx_VCy/BuildType/pvbus.lib.
  • %PVLIB_HOME%/lib/Winx_VCy/BuildType/components.lib.
  • %PVLIB_HOME%/lib/Winx_VCy/BuildType/libarmctmodel.lib.
  • Additional libraries: imagehlp.lib, user32.lib, ws2_32.lib.

System Generator needs access to these header files and libraries for building. The tools automatically include/use them, without them being in the MySubsystem.sgproj project file. Depending on the EVS, additional libraries might be necessary.

Note:

  • Use the /vmg option in the project settings to correctly compile source code for use with SystemC.
  • The TPIP package installation process sets the SYSTEMC_HOME environment variable. The TPIP package is available from the same location as the Fast Models package. This package contains the SystemC and TLM header files and libraries.

Libraries to build the virtual platform on Microsoft Windows

The virtual platform requires specific libraries in addition to the ones the EVS requires.

  • Header file and libraries from the generation of the EVS:
    • Shared library MySubsystem-AConfig.dll.
    • Static library scx-MySubsystem-AConfig.lib.
    • Header file AConfig/gen/scx_evs_MySubsystem.h.
    • Static library scx.lib for the MI simulation infrastructure scheduler mapping, simulation controller, and report handler default implementations, in the directory where the EVS is built.
  • %PVLIB_HOME%/lib/Win64_VCy/BuildType/pvbus.lib, where y = 2008, 2010, 2013; BuildType = Debug, Release.
  • %PVLIB_HOME%/lib/Win64_VCy/BuildType/components.lib.
  • %PVLIB_HOME%/lib/Win64_VCy/BuildType/libarmctmodel.lib.
  • %PVLIB_HOME%/lib/Win64_VCy/BuildType/fmruntime.lib.
  • SystemC library from $SYSTEMC_HOME/lib/Win64_VCy/BuildType/systemc.lib.
  • Additional libraries: user32.lib.

Note:

  • Use the /vmg option in the project settings to correctly compile source code for use with SystemC.
  • The TPIP package installation process sets the SYSTEMC_HOME environment variable. The TPIP package is available from the same location as the Fast Models package. This package contains the SystemC and TLM header files and libraries.

Libraries to package the virtual platform on Microsoft Windows

The virtual platform requires specific libraries.

  • Shared library from the generation of the EVS, MySubsystem-AConfig.dll.
  • libMAXCOREInitSimulationEngine.2.dll.
  • armctmodel.dll.
  • SDL.dll (required only if your model uses the PL041 AACI component or any visualization components).

Depending on the example, additional libraries may be necessary (for example the EVS_LinuxBoot example requires the SDL library). The application searches for such libraries alongside the virtual platform executable that loaded the EVS .dll.

Non-ConfidentialPDF file icon PDF versionARM DUI0835I
Copyright © 2014-2016 ARM Limited or its affiliates. All rights reserved.