for_developers:wrapper_lib
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
for_developers:wrapper_lib [2017/04/17 19:46] – graf | for_developers:wrapper_lib [2017/04/18 12:32] – kalberer | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Create new Wrapper Library ====== | ====== Create new Wrapper Library ====== | ||
- | The following steps have to be taken in order to create a custom wrapper library. | + | The following steps have to be taken in order to create a custom wrapper library. |
- | - Create new CMake project for a shared library. | + | |
- | - Include and link against necessary hardware library. | + | - Create new CMake project for a shared library. |
- | - | + | - Include and link against necessary hardware library. |
+ | include_directories(${FLINK_INCLUDE_DIR}) | ||
+ | link_directories(${FLINK_LIB_DIR})</ | ||
+ | - Create classes for every type you intend to support (AnalogOut, DigitalIn, PWM, ...): | ||
+ | - These classes have to derive from the EEROS HAL classes In- or Output respectively ScalableIn- or ScalableOutput. You can find these classes in the EEROS repository in folder ''/ | ||
+ | - Implement the derived functions for every class. The '' | ||
+ | - For scalable channels '' | ||
+ | - Create a C function '' | ||
+ | - Create all necessary Feature Functions as C functions. These are intended to use for all actions which cannot be called with the derived functions like setting a PWM frequency. | ||
+ | - Create a class to handle the hardware device node ('' |
for_developers/wrapper_lib.txt · Last modified: 2017/04/18 12:43 by kalberer