![]() |
Home · Overviews · Examples |
Qt Jambi is available both in prebuilt and source packages for Linux, Mac OS X, and Windows. Java 1.5 or later is required to install Qt Jambi.
The procedure of installing is different depending on whether you have downloaded a source or prebuilt package. This installation guide has separate sections for each approach.
Enjoy !
To run the examples and demo launcher on Windows run the
qtjambi.exeexecutable from the Qt Jambi directory. On Linux and Mac OS X run the
qtjambi.shshell script from the Qt Jambi directory.
Running these files will verify the virtual machine version and set the correct environment for running Qt Jambi applications.
When you are ready to distribute your own applications, see the deployment document. To run the examples or launcher, the classpath must also include the qtjambi-examples-4.4.0_01.jar. An alternative way of loading the native libraries is to rely on Java's standard method of loading native libraries. This is done by specifying either the JVM system property -Djava.library.path=[path_to_libraries] or setting the following environment variable: Manually Launching Qt Jambi Applications
To manually run Qt Jambi, the qtjambi classes archive and qtjambi platform archive must be available in the CLASSPATH. The qtjambi classes archive is named qtjambi-4.4.0_01.jar and the platform archive is named according to the operating system and compiler used to generated the native binaries, such as qtjambi-win32-msvc2005-4.4.0_01.jar // Linux
java -cp qtjambi-4.4.0_01.jar:qtjambi-linux32-gcc-4.4.0_01.jar:qtjambi-examples-4.4.0_01.jar com.trolltech.launcher.Launcher
// Mac OS X
java -XstartOnFirstThread -cp qtjambi-4.4.0_01.jar:qtjambi-macosx-gcc-4.4.0_01.jar:qtjambi-examples-4.4.0_01.jar com.trolltech.launcher.Launcher
// Windows
java -cp qtjambi-4.4.0_01.jar:qtjambi-win32-msvc2005-4.4.0_01.jar:qtjambi-examples-4.4.0_01.jar com.trolltech.launcher.Launcher
Note: When running a Qt Jambi application on Mac, it is necessary to pass the -XstartOnFirstThread argument to the Java executable.Alternate way of loading native libraries
Qt Jambi must be enabled to find the native libraries. The Qt Jambi libraries is a set of class files contained in the qtjambi-4.4.0_01.jar file and a set of native libraries. The native libraries are located in a .jar file named according to your operating system, hardware configuration and the compiler that was used to build the package, for instance qtjambi-win64-msvc2005x64-4.4.0_01.jar. The native libraries will be automatically loaded when this jar file is part of the classpath. Windows Set the PATH environment variable to include the bin directory in the Qt Jambi directory. Linux Set the LD_LIBRARY_PATH environment variable to include the lib directory in the Qt Jambi directory. Mac OS X Set the DYLD_LIBRARY_PATH environment variable to include the lib directory in the Qt Jambi directory.
Some of Qt's functionality is loaded via native plugins. This includes for instance support for jpeg images. When using the platform archive, plugins are configured and loaded correctly automatically. When loading native libraries from the file system, Qt will try to load plugins from the directories in the QT_PLUGIN_PATH environment variable.
You are then ready to run Qt Jambi applications. An example of how to run the launcher manually is illustrated below: Note that a source package requires a Qt to be built. To avoid potential binary incompatibilities it is highly recommended that you build both Qt from scratch before building Qt Jambi from source. On Mac OS X, Qt must be configured without frameworks (by running the configure script with the --no-framework option). You will find more information in the Qt Designer document. To build the generator example from the source package simply do:Building Qt Jambi from a Source Package
This section describes how to build Qt Jambi from source. We first explain how to configure your system, and then we go through the procedure of building Qt Jambi from the command line. Finally, we look at some common installation problems. Configuring the System for Qt Jambi
The Jambi source package requires a Qt source package, JDK 1.5 or higher and the build utility ant.Building Qt for Qt Jambi
The first step is to build Qt for Qt Jambi. A normal Qt build will normally work, but there are a few exceptions. For more details on building Qt on any given system see the Qt installation guides. All Some featuers in Qt are turned on or off for Qt Jambi by configuring with -D QT_JAMBI_BUILD. Qt Jambi also has no need for the Qt 3 support library so it is recommended to compile with -no-qt3support. Mac OS X Qt Jambi only supports Qt configured with -no-framework and because of compatibility it is recommended to configure Qt against the 10.4 SDK, -sdk /Developer/SDKs/MacOSX10.4u.sdk Linux Sun's Java Virtual Machine has a bug preventing it from using MMX and SSE instructions. For deployment against 1.5 Java runtimes, configure Qt with the options -no-mmx -no-sse -no-sse2 -no-3dnow to avoid problems. Windows (MSVC 2005 or newer) -D QT_JAMBI_BUILD is required for plugins to properly load. Setting up the environment
The following table describes the environment variables necessary to install Qt Jambi. QTDIR This variable must contain the path to the directory where Qt is installed. JAVA_HOME This variable must contain the path to the directory where Java is installed. QMAKESPEC This variable is redundant in most cases, but may be required to pick between ambigous compilers, such as MinGW or MSVC on windows. Building Qt Jambi
Qt Jambi provides a ant task which handles all the tasks of building the Qt Jambi libraries. To build Qt Jambi simply make sure the above requirements are met and type> ant
in the Qt Jambi directory. Please note that Qt Jambi requires the ant-trax module of ant which is optional in some linux distributions. Running ant will automatically go through the following = steps:
For a description of the various sub-targets of the ant build one can:> ant -projecthelp
For a description of the various build configurations, one can do:> ant help
Trouble Shooting
If you have trouble compiling and running Qt Jambi, we present problems that are commonly encountered in a table. This should be sufficient to solve most problems; failing that, try asking someone. The Jambi FAQ is a good place to start. In the Jambi Mailing List, active Jambi users and the Jambi development team can be helpful with installation problems; please run Qt Jambi with the com.trolltech.qt.verbose-loadingsystem property and give stack traces if Qt Jambi fails to load native libraries.Common Problems
In this section, we have tried to gather common problems encountered while building Qt Jambi. They are listed in a table with columns for the problem description and solution. On Linux the gcj (GNU Java Compiler) is located in /usr/bin; the path to the correct java version must be before this in the PATH. This usually results in java.lang.ClassFormatError errors. Make sure that it is the correct java executable in the PATH. Environment variables are not set correctly. Check with the Configuring the System for Qt Jambi section that your system is properly configured for Jambi. Qt Jambi uses the Qt Header files to generate the mapping from c++ to java. Unless Qt was built with default settings, you may get link problems for bindings that are not in the native libraries. Build Qt with default settings juic does not update .jui files that are not modified, which can be a problem if Java sources are deleted. Run juic with the -a option. Qt Jambi expects that Qt was built with debugging turned off. If Qt was built with debugging, the libraries will not be found. Run Qt Jambi with the com.trolltech.qt.debug system property. Load Issues
If Jambi cannot find the native libraries, you will get java.lang.UnsatisfiedLinkError's or other load issues. The search paths - in the order Jambi searches - for libraries are listed below. Platform Notes
Mac OS X When running a Qt Jambi application, it is necessary to pass the -XstartOnFirstThread argument to the Java executable. Also, if you have a source package, you have to build Qt with the --no-framework option. Linux / 64 bit: Install a 32 bit virtual machine, e.g., on Ubuntu, install the ia32-sun-java5-bin package and put /usr/lib/jvm/ia32-java-1.5.0-sun-1.5.0.06/jre/bin into the PATH environment variable. Running the Qt Designer
The Qt Designer is Trolltech's tool for designing and building user interfaces. If you have a prebuilt package, you can run it from the command line with the designer.bat or designer.sh scripts. The Eclipse integration handles the designer automatically. Running the Qt Jambi Generator
The generator is a Qt application which can be used to map C++ based Qt APIs onto equivalent Java APIs. The Qt Jambi package provides an example on how to use the Qt Jambi Generator, located in the path/to/Qt Jambi/generator_example directory. ant -f build_generator_example.xml
Warning: The Qt Jambi generator is written to handle Qt based source code, and is not intended for mapping C++ libraries in general.
Copyright © 2008 Trolltech
Trademarks