System API and Library Calls
Ensuring you can build a code base for a platform requires validating the API's and any linked libraries are available for your targets. To this, we have compiled a chart broken down by platform or standard library that has the functions called throughout the library; this is in an effort to help you determine if you can deploy the functions of Omni you wish to use for the platforms you want to target.

It should be noted that depending on how you build the library (i.e. what options you use to compile Omni), can affect which functions are called. For example, if you compile Omni on a Windows platform with the OMNI_NO_WIN_API flag defined, the _beginthreadex API will be used instead of the CreateThread API; for more information on what compile options are available and what effects they have on the library, please see the compile options documentation.

Also, please note that these lists do not include the specific types used throughout the library; for example, the C++ list does not contain std::string nor does the POSIX list contain pthread_t. If you wish to see which types are used, since certain types will vary based on platform, you can visit the class index and browse for any classes, struct's, or typedef's that end in _t. Alternatively, you can view the individual headers that are included with the base_types header, which includes the various types used and defined throughout the library.