Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


We therefore end up with a "library" project and an "application" project. An example of such a pair can be found at; the source is at

Building an "includes" zip

We need to make the .h and .so/.dll files from the library project available when compiling the application project. To do this, I've configured the pom of the library project to build a zip file containing the includes files; until MDEP-47 is fixed, . We also put the .so also has to go file in the zip file (if we had MDEP-47, we could extract it from the jar), as it's much easier to extract from there, it separates runtime and compiletime dependencies more nicely, and because we might as well.

Here's an example assembly descriptor (which can be packaged into the shared build-scripts artifact as below):