Installation of cyloop
This page describes the installation of Cyloop on a computer with
an operating system coming from UNIX, such as GNU/Linux.
Installation on another operating system depend on how work the
tools you use (Un archiver and C compiler).
If you recovered the source file compressed, first uncompress
gunzip cyloop.tar.gz or
Place the file cyloop.tar in the directory of your
choice and unpack it :
If you recovered the file cyloop.zip the command that performs
both the decompression and unpacking is :
If you recovered an update (file majcyloop.tar or equivalent
compressed), see note at end of paragraph.
The different files will be copied into a subdirectory cyloop
Go into that directory and run :
to compile sources.
If you recovered a compressed file with executable programs, the
installation is done similarly, but without having to run make
gunzip cyloop-bin.tar.gz or
or unzip cyloop-bin.zip
Note : If you recovered an update
(majcyloop.tar file or a compressed version), you must position
yourself directly above the cyloop directory that contains files
from an earlier version.
Unpacking file majcyloop.tar and compiling modified sources, is
then performed as described above.
Recovery and installation of font files
Font files are data files that can give extended character set for
text embedded in graphics generated by the command cylgraph .
In early versions of Cyloop for greater flexibility in the evolution
of the source files as font files, font files are provided separately.
Retrieve a file from :
fontecyloop.tar.bz2 or fontecyloop.zip
or an update majfontecyloop.(...)
Uncompress and unpack it like you did for the source files.
You can either install the font files before or after the compilation
of source files.
Local or system directories installation
Cyloop executables are ready, but the operating system does not
necessarily know where they were installed.
If you want to keep Cyloop in a specific directory, you will need to
add access to the subdirectory cyloop/bin in the PATH
environment variable .
To do this, you must directly modify a file where the PATH variable
is declared, either the file /etc/profile if Cyloop was installed
for multiple users, or the file .bashrc or .bash_profile
in your account otherwise.
In all cases, put an absolute path to the directory location of
You will need to reconnect (login) for the new path is taken into
If instead you want Cyloop either the same location as the other
commands of your operating system, namely in /usr/bin, after the
initial installation (completed by the make command if you
installed Cyloop from source files), you must switch to super user
(root) to run from the directory where Cyloop is implemented, the
Cyloop can then be used by all users of the computer without having
to modify the environment variable PATH .
Selecting a default language
The various Cyloop analyze the environment variable $LANG to choose
the language of the user interface.
Accordingly, if the environment variable $LANG is not set, or if it
refers to a language not available, Cyloop can only work as long as
no message is sent to the user.
This is the case for most cyloop commands as they work without errors,
but not the first to use, namely cylcree command.
To use Cyloop in this case it is necessary to create a data file
mess-cyloop for a language chosen by default.
This file will have to be located in the same directory that the files
corresponding to different languages of cyloop :
The name of this file is obtained by removing the language suffix (a
. followed by 2 letters) of the file from which it has been
- in the installation directory cyloop/bin if cyloop has been
- in the directory /usr/share/cyloop if cyloop was installed
in /usr/bin with the other operating system commands.
For proper operation of the default language, avoid using files whose
name ends with -utf .
To create the files in the default language, it is advisable to make
symbolic links instead of copies or real links of the file. Thus, if
the language file changes, there will be nothing to change for the
For example, to select English as the default language, you run the
ln -s mess-cyloop.en mess-cyloop
If you want the default language file to be always used (ie, without
taking into account the environment variable $LANG),
you must add a file named deflang-cyloop (it can be empty) in
the directory containing Cyloop commands or in /usr/share/cyloop
depending on how Cyloop has been installed.
Installing the documentation
As for the Cyloop application files, begin by making a local
installation. Then it will be possible to put the Cyloop man pages
with the other man pages of the operating system.
If the file containing the documentation is compressed, start by
uncompressing it :
(or similar command with another file).
Unpack the file containing the documentation :
tar -xvf doccyloop-fr-utf.tar
tar -xvf doccyloop-fr-iso.tar
tar -xvf doccyloop-utf.tar
tar -xvf doccyloop-iso.tar
(or similar command with another file).
cyloop subdirectory will contain one or more presentation
files (one file per language installed), as well as man pages in
subdirectories of cyloop/man .
More specifically, the man pages will be installed in the
with ?? which is a language among : fr es pt eo .
for the English language,
for another language.
For languages other than English, the name of the documentation file
contains -utf or -iso to indicate the accented set of
characters used (UTF-8 and ISO8859-1).
If your man pages are not displayed or displayed with a wrong
character set, just use the other documentation file.
If you chosed to implement Cyloop in /usr/bin with the other
operating system commands, it is desirable that the Cyloop man pages
to be installed in /usr/share/man
For this in superuser mode (root), from directory cyloop you
can run the command :
It is also possible to move man files via 2 mv commands rather
than making a copy. For the man pages in French, commands will
find man | cpio -pdmuv /usr/share
mv man/man1/* /usr/share/man/man1
mv man/man5/* /usr/share/man/man5
In the case of a local installation of Cyloop and its documentation,
if the PATH has been initiated to find the executable files in
.../cyloop/bin , man pages located in .../cyloop/man are
If this is not the case, you can correct the problem by adding a path
to environment variable MANPATH .
If this environment variable was not declared, (frequent), simply add
to /etc/profile (you must be root for that), or on its your
account in the file .bashrc or .bash_profile, 2 lines
(assuming you were in /home/xxx when you have unpacked the
The man pages will be accessible after the next login.