libFAUDES/DESTool is developed in a Linux environment, so one would think, deployment for that platform is particularly easy. The contrary is the case ...
Until there is an automated installation script, DESTool must be manually unpacked. This is perhaps a bit old fashioned, but not difficult.
Download the latest archive faudes_destool_x_xx.tar.gz from our online archive.
Extract the archive somewhere in the users file system. System wide installation is currently not supported. Extraction will look something like this:
> mkdir ~/here_should_detool_go > cd ~/here_should_detool_go > tar -xzf ~/Download/faudes_destool_x_xx.tar.gz
You can now start DESTool by
> cd ~/here_should_detool_go > ./faudes_destool_x_xx/bin/destool
When DESTool starts, you can use the About menu to verify versions and available plug-ins. There should be at least the VioGenerator plug-in, which is responsible for graphical representation of generators.
If you get errors on missing libraries or other obscure messages before even the DESTool welcome screen shows ... stay calm, presumably there is nothing big missing.
We have verified DESTool do operate on old installations like SUSE 10.0 32bit (dated 2005) up to Fedora 14 64bit (dated 2010). Technically, DESTool is dynamically linked against the so called LSB library stubs in their 32bit version. While this type of linkage is meant to increase binary compatibility, on some distributions manual installation is required. To list present LSB modules, try:
> lsb_release
Among the listed modules, there is a module core-3.0-ia32 core-3.2-ia32 or even core-4.0-ia32: you should be fine.
No modules reported at all (just something like command not found): LSB support is not installed, see below.
There are ...-ia32 modules, but the highest version number is core-2.1-ia32: the distribution is just too old, sorry.
All reported modules are ...-ia64: try installing 32bit LSB support (see below); however, if your package manager indicates a huge amount of dependent missing packages, your installation is not prepared for 32bit software at all; please contact me, so I can see to produce a 64bit binary of DESTool.
Examples on how to install LSB packages ...
... on Ubuntu 10.04, both 32-bit and 64-bit distributions.
> aptitude install lsb > aptitude install lsb-desktop
... on Fedora 14, 32-bit distribution
> yum install redhat-lsb > yum install redhat-lsb-graphics
... on Fedora 14, 64-bit distribution
> yum install redhat-lsb > yum install redhat-lsb-graphics > yum install redhat-lsb.i686 > yum install redhat-lsb-graphics.i686
If you still experience errors for missing libraries or unresolved symbols, please let us know.
DESTool uses Qt 4.4 as a GUI framework. To operate on older Linux installations that do not provide Qt 4.4, DESTool ships with a customized copy of Qt 4.4 (linked against LSB library stubs, see above). If, on the other hand, one installs DESTool on a more recent Linux installation, it may be preferable that DESTool uses the installation's version of Qt. This will have a more consistent look & feel and, presumably, be more stable than the one that comes with DESTool.
To test which version of Qt came with your Linux distribution, try
> qmake -v
If your systems Qt version is 4.5 or above, it is recommended to delete the QT 4.4.2 from the DESTool package. This can be done as follows.
> cd ~/here_is_destool > rm ./faudes_destool_x_xx/lib/libQt* > rm ./faudes_destool_x_xx/lib/q*.bin > rm ./faudes_destool_x_xx/lib/plugins/imageformats/* > rm ./faudes_destool_x_xx/lib/plugins/sqldrivers/* > rm ./faudes_destool_x_xx/lib/assistant.lib > rm ./faudes_destool_x_xx/bin/assistant
The DESTool online help is managed by Qt's assistant. This is really a great tool, however, we have observed hick-ups somehow related to cached states/files. You may decide to delete the assistant's cache ... if you find it. Try
> mv ~/.assistant ~/assistant_delete_later > mv ~/.local/share/data/Trolltech/Assistant ~/assistant_delete_later
Note: when removing the assistant's cache you will lose assistant bookmarks and local copies of any help-files.
Most of the above deployment issues come from binary distribution, so why not make DESTool open source?
Honestly, the source is currently just not in a shape that allows for effective collaborative development. There is the intention to release the sources under GPL terms, once it makes sense to share. Crucial conditions, that are currently not satisfied, include:
build process to be triggered by one simple qmake (as opposed to a bunch of shell scripts);
clean and well documented interface for visual representations of faudes-objects;
fix at least the five most irritating design flaws that sneaked in due to laziness and pragmatism.
If you would like to inspect the situation in detail, perhaps to contribute to the further development of DESTool, please let us know.
libFAUDES 2.24a --- 2014.04.04 --- with "synthesis-observer-diagnosis-hiosys-iosystem-multitasking-coordinationcontrol-timed-simulator-iodevice-luabindings"