DESTool on Linux

libFAUDES/DESTool is developed in a Linux environment, so one would think, deployment for that platform is particularly easy. The contrary is the case ...

Step by Step

Until there is an automated installation script, DESTool must be manually unpacked. This is perhaps a bit old fashioned, but not difficult.

Missing Libraries

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 a range of 64-bit Linux distributions, including Ubuntu 10.04 LTS, Fedota 14 (2010) and various versions of plain Debian (2014). There is also a 32-bit version of DESTool available, compatible back to SUSE 10.0 (2005). However, the 32-bit version is only updated upon request -- let us know if you need a recent 32-bit binary.

Technically, DESTool is dynamically linked against the so called LSB library stubs. While this type of linkage is meant to increase binary compatibility, on some distributions manual installation of an LSB loader is required. To list present LSB modules, try:

> lsb_release

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, both 32-bit and 64-bit distributions:

> yum install redhat-lsb
> yum install redhat-lsb-graphics

... on Fedora 14, 64-bit distribution to run 32-bit DESTool:

> 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.

Inconsistent GUI Style - Broken Online Help

DESTool uses Qt 4.8 as a GUI framework. To operate on older Linux installations that do not provide Qt 4.8, DESTool ships with a customized copy of Qt 4.8 (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.8 or above, it is recommended to delete the Qt libraries 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 not in a shape that allows for effective collaborative development. There is the intention to release the source under GPL terms, once it makes sense to share. Core requirements include:

If you would like to inspect the situation in detail, perhaps to contribute to the further development of DESTool, this can be aranged



libFAUDES 2.28b --- 2019.12.01 --- with "synthesis-observer-diagnosis-iosystem-hiosys-multitasking-coordinationcontrol-timed-iodevice-simulator-luabindings"