How to install the Thot Editor Release

Home

Downloading

Installing

• Sources
• Binaries

Compiling

Using

Developing

Installing the Source Tree

Below is explained how to uncompress and expand the source archive for Thot Editor.

Since Thot Editor is an application built on top of the Thot library, the sources tree contains both sources for the library and the editor.

We assume that the source archive thoteditor-src-yyy.tar.gz (where yyy is the Thot Editor version number) have been fetched from INRIA server, and stored in /tmp :

Current version numbers is 2.1e for Thot Editor.

The platform list enumerate the Targets for which Thot have been compiled and tested by the project team.

The source tree is created by invoking the following commands in the directory of choice (it will create the Thot sub-directory):

> gunzip -c /tmp/thoteditor-src-yyy.tar.gz | tar xvf -

Be sure to have plenty of room available, compiling a debug version of Thot Editor can use up to 150 Mbyte of disk space.

The source tree is made of the following directories:

• batch directory contains the sources for the schema compilers.
• config contains all the dialogs messages files both for English and French, as well as a few configuration files like the Thot registry (stored in file thot.ini).
• dicopar directory holds the dictionnaries and hyphenation rules.
• doc contains the programming documentation for Thot library and languages,

  the sub directory thoteditor contains the documentation for the Thot Editor.

• drawlib directory contains the structured graphics library.
• fonts directory contains a few X-Windows specific fonts needed by Thot editor.
• indexlib directory contains the index library.
• libjpeg and libpng contains the sources of two graphic libraries needed by Thot toolkit.
• misc/tools directory contains the source of the tool rescandialogue.c that allows to update a language specific dialog tables.
• schemas directory contains the structure, presentation and translation schemas used by Thot editor.
• tablelib contains the table library.
• thot directory contains the Thot editor application source code.
• thotlib directory contains the Thot library sources. The headers defining the interfaces exported by the library are in the include sub-directory.

See next step Compiling Thot Editor for more information on how to populate this subtree.

Installing the Thot Editor Binaries

Below is explained how to uncompress and expand the Thot Editor binary distribution.

We assume that the archive thoteditor-Platform-yyy.tar.gz (where Platform is the platform your machine type and yyy is the Thot Editor version number) have been fetched from INRIA server.

Current version number is 2.1e.

The platform list enumerate the Targets for which Thot Editor have been compiled and tested by the project team. If your machine does not belong to one of these you can get the source distribution and try to build Thot following the compiling instructions.

Choose a place for Thot

Supposing the binary distribution was loaded fine, one must choose a place to install it. We suggest

• /usr/local for a system wide installation

• the user home directory for a personnal installation

Depending on the platform you are using, Thot editor requires from 7 to 10 Megabytes of disk space.

Extract the distribution

Move the distribution to this directory, check that the rights on this directory allow you to create a directory and extract the distribution.

The Thot tree is created by invoking the following commands in the directory of choice (it will create the Thot sub-directory):

> gunzip -c /tmp/thoteditor-Platform-yyy.tar.gz | tar xvf -

The Thot tree is made of the following directories:

• batch directory contains the graamars used by schema compilers.
• config contains all the dialogs messages files both for English and French, as well as a few configuration files like the Thot registry (stored in file thot.ini).
• dicopar directory holds the dictionnaries and hyphenation rules.
• doc contains the programming documentation for Thot languages, the sub directory thoteditor contains the documentation for the Thot Editor.
• fonts directory contains a few X-Windows specific fonts needed by Thot editor.
• schemas directory contains the structure, presentation and translation schemas used by Thot editor.
• A Target directory (solaris2, LINUX-ELF, osf, etc.) contains the compiled binaries of Thot Editor, Thot languages compilers and the print deamon.

Set up the environment and start Thot Editor

The file Thot/Target/bin/thot is the Thot editor binary, the best thing is to add the path to the Thot/Target/bin directory to your PATH environment variable. For example on a Linux-ELF system:

setenv PATH $PATH:/usr/local/Thot/LINUX-ELF/bin

for a csh or tcsh shell. When using sh, bash or another variant of the Bourne shell

PATH=$PATH:/usr/local/Thot/LINUX-ELF/bin ; export $PATH

Maybe this command should be added to the .login startup script. Once done one can lauch Thot editor simply by typing "thot" to the shell prompt. The Thot main window should open. You can open the Thot manual, it is in the Thot/doc/thoteditor directory of the distribution.

If something goes wrong

If Thot doesn't seems to work, check the following points:

1. The DISPLAY variable is correctly set

2. Remove your previous registry file $HOME/.thotrc if neccessary.

3. The binary just installed is the correct one, i.e. it is the correct binaries for the current machine

   (don't try to start the Linux-ELF version on a Solaris machine or an old Linux a.out installation).

4. If the binary version is ok, check the availability of the dynamic libraries needed by the executable file thot (located under Thot/Target/bin). for example on a Linux-ELF system type:

   ldd Thot/LINUX-ELF/bin/thot

   and check that there is no missing libraries.

One can install packages for different platform under the same directory (for example on a server filesystem exported via NFS to an heterogenous set of machines), use the appropriate PATH on each platform.

All the traffic on the Thot mailing-list is archived here. Please have a look at it before sending us mail if something goes wrong. Remember, it's an Beta release.