5.6. EC-Monitor Source Code

In a source code delivery the EC-Monitor sources are divided into 4 parts:

  • SDK Header files

  • Link layer files (multiple Link Layers may be shipped)

  • Link OS layer files (only valid for the Link Layers)

  • EC-Monitor files (configuration, core and interface layer)

  • OS layer files

The EC-Monitor can be ported to several different operating systems and CPU architectures with different compilers and development environments. Typically no supported build environment files like IDE projects are shipped with the source code.

To build the EC-Monitor the appropriate build environment for the target operating system has to be used. If an integrated development environment (IDE) exists (Visual Studio, Eclipse, etc.) several projects containing all necessary files are needed to build the artefacts. If no integrated development environment is available makefiles and dependency rules may have to be created which contain the necessary EC-Monitor source and header files.

For most platforms three separate independent binaries will have to be generated:

  1. Link Layer Binary. The Link Layer binary will be dynamically bound to the application at runtime.

  2. EC-Monitor Library

  3. Remote API Server Library

5.6.2. EC-Monitor Binaries

The following files have to be included into an IDE project or makefile:

  • EC-Monitor files

  • OS layer files

  • For all platforms a static library has to be created. This library will have to be linked together with the application.

5.6.3. Remote API Server Binaries:

The following files have to be included into an IDE project or makefile:

  • Remote API server files.

  • For all platforms a static library has to be created. This library will have to be linked together with the application.

See also

Platform and Operating Systems (OS) for required tool chain settings