This allow us to have a better compatibility with allmost JVMs, without depends if the JVM implements or not some libraries (e.g: if your JVM don’t implements Java Sound Api, so you can run tuxguitar without tuxguitar-jsa plugin ). Another advantage is that anyone can write plugins for tuxguitar even after a version was released. The source package contains all project folders, but you don’t should try build all plugins for your Operating System. There are some plugins what have native libraries, so they aren’t multi-platform.Įxploring the TuxGuitar folder, you’ll found build.xml and build.properties files. It contains standart targets to build, package, and clean the sources. Installation path for the tuxguitar launcher.īuild.xml file, will take the configuration from build.properties and call $/ All of this targets will call to another target of a child file if “dist.file” property exists. Once you have configured build.properties, you must execute ant command on a terminalĪll tuxguitar plugins are compiled in a similar way. As the main application, they have build.xml and build.properties too. ~$ cd tuxguitar-src-1.0-rc4/TuxGuitar-compat We can take TuxGuitar-compat plugin as example: (Required by plugins what use GUI libraries)įull path to itext.jar or itext classes folderĪs the main application, you just need execute ant command on a terminal Generate class files for specific VM version (Is suggested add same value as used for build tuxguitar)įull path to tuxguitar.jar or tuxguitar classes folderįull path to swt.jar or swt classes folder Provide source compatibility with specified release (Is suggested add same value as used for build tuxguitar) You just need edit build.properties of the plugins you want to build. Ofcourse you may want to build the main application and some plugins together.
0 Comments
Leave a Reply. |