Deployment of Babel Enabled Libraries
At this point, there is no standard -- or even recommended -- model for
deploying Babel enabled libraries. Below are a few examples of how our
developer-customers are currently packaging their code.
- Server Source Only
- With this option your users are expected to have Babel installed on their
system. In this mode, developers simply include a SIDL file and their
corresponding implementation files. The user in this case must build the
software, call Babel to generate the client bindings in the language of
choice, and link it all together into a final application.
- Client and Server Source
- This option tries to hide Babel as much as possible. In this mode, the
developer pre-generates many different client language bindings and
distributes them along with their code and the sources for the Babel
runtime library. Then the user has a ``batteries included'' package
that's ready to run out of the box. The user may not even be aware that
Babel has been used unless they pay careful attention to how the package
was built.
- Server Libraries Only
- Finally, in this mode only the SIDL file and the precompiled shared library
files are distributed. This is not an open-source solution, though users
still need to build the language bindings to access the shared library.
babel-0.10.2
users_guide Last Modified 2005-03-23
http://www.llnl.gov/CASC/components
components@llnl.gov