Library Header Files

If the platform requires application code to #include platform-specific header files, these should reside in a subdirectory of the platform directory pointed to by the sdx:includePaths attribute for the corresponding OS in the platform software description file.

For a given sdx:includePaths=”<relative_include_path>” in a platform software description file, the location is:
<platform root directory>/<relative_include_path>

Example:

For sdx:includePaths=”aarch32-linux/include”:
<sdx_root>/samples/platforms/zc702_axis_io/sw/aarch32-linux/include/zc702_axis_io.h
To use the header file in application code, use the following line:
#include “zc702_axis_io.h”

Use the colon (:) character to separate multiple include paths:

sdx:includePaths=”<relative_include_path1>:<relative_include_path2>”
For example in a platform software description file that defines a list of two include paths:
<platform_root_directory>/<relative_include_path1>
<platform root_directory>/<relative_include_path2>
Remember: If header files are not put in the standard area, users need to point to them using the –I switch in the SDSoC environment compile command. We recommend putting the files in the standard location as described in the platform XML file.

Static Libraries

If the platform requires users to link against static libraries provided in the platform, these should reside in a subdirectory of the platform directory pointed to by the sdx:libraryPaths attribute for the corresponding OS in the platform software description file.

For a given sdx:libraryPaths=”<relative_lib_path>” in a platform software description file, the location is:
<platform_root>/sw/<relative_lib_path>

Example:

For sdx:libraryPaths=”aarch32-linux/lib”:
<sdx_root>/samples/platforms/zc702_axis_io/sw/aarch32-linux/lib/libzc702_axis_io.a
To use the library file, use the following linker switch:
-lzc702_axis_io
Use the colon : character to separate multiple library paths. For example,
sdx:libraryPaths=”<relative_lib_path1>:<relative_lib_path2>” 
in a platform software description defines a list of two library paths
<platform_root>/sw/<relative_lib_path1>
<platform root>/sw/<relative_lib_path2>
Remember: If static libraries are not put in the standard area, every application needs to point to them using the –L option to the sdscc link command. Xilinx recommend putting the files in the standard location as described in the platform software description file.