Bartko, Zoltan wrote: > So if I use the first approach (c++ lib + Qt-glue + Jambi glue + java), do > I a) have to recompile all of Jambi to get a platform-specific jar file > or > b) is there any way to have a directory, where I would have the > platform-specific libraries of hunspell + qt? >
a) If you wish to bind up new C++ libraries that are based on Qt, you will definitely need to recompile Qt Jambi, because your C++ libraries will depend on a specific version and configuration of Qt, and you need to have native libraries for Qt Jambi which is compiled against this exact version in order to maintain binary compatibility. b) It is not strictly necessary to use a .jar based approach for deployment. You can place all native libraries in a directory on the disk and make sure this directory is present in the PATH/LD_LIBRARY_PATH environment variables before running your application. We do recommend using the .jar based approach when deploying applications, however, since using PATH will leave loading of the native libraries up to the operating system, which means you can potentially get BC bugs that are hard to track down e.g. when deploying on machines that already have the Qt libs installed in the system directories. Setting up an environment that works and using the PATH based approach while developing, however, is probably preferable, since it's less work for each debugging iteration. -- Eskil _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
