On Thu, Jun 21, 2012 at 10:15 AM, Gordon Sim <[email protected]> wrote: > On 06/21/2012 02:19 PM, Rajith Attapattu wrote: >> >> For the Java binding, the generated code (compiled into a jar file) is >> checked into the java lib dir. > > > Generating it and compiling it is a manual step? This is all done automatically. CMake has good support for both Swig and Java :)
> Does that not depend on the swig 'control file' (apologies, I'm not familiar > with the correct > terminology)? Yes the instructions to generate the java files (using swig) and compiling/creating the jar is done using Cmake file [1]. > What are the build artefacts involved, what are the source components for > each of them and where d these sources live? The swig files live in binding/ and binding/qpid/java The build artefacts are the libcpqid_java.so and a jar file. > > >> I see no way around it, unless you make the java build (for the cpp >> based api implementation) conditional on the cpp build, which is not >> going to fly. > > > Again, what you need is just the public headers files (for swig generation > and compilation of the native component of your library) and the message lib > (which you would require at runtime anyway). I just responded to Andrew's specific question about checking in generated code. Not really about the versioning debate. Yes you are correct, I only need the C++ header file during build time. Does the above answer your questions sufficiently ? [1] https://svn.apache.org/repos/asf/qpid/branches/address-refactor2/qpid/cpp/bindings/qpid/java/CMakeLists.txt > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
