Libraries - Third Party
Integration with any required third party library can be accomplished easily in Bedrock, whether it be with Java JARs or native libs for native platforms.
Java
Stub libraries for the common mobile JSRs are included in Bedrock, but any additional JSRs may be included as simple stub references at compile time.
Additionally, any third party or in house J2ME library can be integrated into the build process of any project. This will be integrated into any generated Eclipse / NetBeans project information and included in any built JAR as required.
Where the source code for a third party library is available, the developer gains the additional benefit that Bedrock's cross-compiler can be utilised that convert this library to native platforms, enabling their usage on all the platforms Bedrock supports. Examples of libraries that this has been tested on include:
- LWUIT
- J2MEUnit
- BouncyCastle
Native
Native libraries (any standard lib/dll/so/dylib for a particular target) can be integrated for native platforms as part of those handsets' build process. A range of options are provided to automate the library injection, including into any automatically generated project files. If required it is very simple to generate a wrapper back into Java for each library so it can be manipulated from the project source code, alternatively you can natively patch the generated C++ to interface as required.
Features
- Ability to define and include any native library into the Bedrock build process
- Injection of such definitions into makefiles and DevStudio/XCode projects for debugging convenience
- Where required, ability to supply overrides of the default templates for the above (makefiles / IDE projects)
- Customisable callbacks and hookpoints in the Bedrock run-time libraries at key points (e.g. if a library needs to run from a particular core thread, or be initialised before the application code loads)
