This is what we do in the Windows and generic Linux installers. Include the JRE in the Jitsi installation package.like Debian’s dpkg and apt-get do), then this is probably the best option, as it only consists in indicating that installing your package requires installation of the package containing SUN’s JRE. Dependency - If the packaging system that you are using allows it (e.g.There are three approaches you may choose when dealing with this issue: In order to run Jitsi, users would need a locally installed Java Runtime Environment, and it is the responsibility of the installer to make sure that a compatible JRE exists on the user machine. ) in order to tune the installation package and make it work on the destination operating system, but these depend on the cases and are outside the scope of this tutorial (and besides it’s getting late here and I want to go to bed). You may of course have to add other properties (e.g. Note that the exact location of the libraries depends on the location where your installer would place them. classpath "/usr/share/lib/jdic_stub.jar:/usr/./util.jar" You would have to enumerate all of them in the classpath property of your run command: We mentioned these jars in the previous section. You should also add to the classpath all library jars that Jitsi needs and does not include in the OSGi bundles. file=/usr/share/sip-communicator/lib/logging.properties \ #java =file:/usr/share/sip-communicator/lib/ \ The tutorial assumes that before trying to build the installer, the user would have succeeded to build that application (by executing “ant build” in the project directory). It tells you how you should be executing it, which libs and bundles you should be including in your distribution package and indicates those that you should not. This tutorial goes over details that one would need to know in order to build an installation package for Jitsi by only using its sources. These steps generally include things like setting the classpath, choosing a Java virtual machine or making sure that the executable is in the OS $PATH variable. The task also includes defining a set of steps (often in a script) that would need to be executed on a host machine when the application is installed so that it is properly configured for its first launch. Creating an OS specific installer for Jitsi (or any other Java application for that matter) consists in packaging all necessary binaries in a single installation package, which could be an archive, an executable, or both.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |