Technical Documentation: Building and Installation

From Go4IT project

for the anxious

Anxious HOWTO

   cd Go4IT/package2/build
   ./autogen.sh
   ./configure
   make
   make install

for the rest

Intro

You can find required scripts in it in the svn repository in Go4IT/package2/build folder. Current build scripts execute without any change in the original files of each sub-module (Compiler, rts, TM_Core, TM_UI and TL. For future versions, rearrangements of the code of each module should be considered.

The content of build scripts is based on those provided for each module. The mainn difference is that they are generated with the GNU autotools to ease the work of porting across platforms. The targets for the TM-* and TL modules are built twice: once using the Go4IT headers (to be used with picottcn) and once using telelogic-compatible headers (with -DCOMPAT_TAU_2_7 --> to be used with tau tester).

Requirements

The general and particular requirements are:

• GNU/Linux
• GNU gcc/g++ (>=4.1)
• GNU flex (>=2.5.33)
• GNU bison (>=2.3)
• jdk (>=1.6)
• GNU make (>=3.80)
• GNU autoconf (>=2.61)
• GNU automake (>=1.8)
• GNU libtool (>=1.5)

More detailed building

Even though the procedure to have it running is the one presented at the for anxious section, there are some useful things to comment about.

If compilation fails in a module, the building process will abort. This must not happen when we reach a stable version, but can happen right now. If so, you can try to fix the problem (if you know what you are doing) and send the solution to the maintainer of the module. If you are not able (don't have time) to fix it, please send an e-mail to the maintainer or add the bug to the mantis bugtracking system. Building will not work until the problem is fixed.

Generating executable DNSTester for debugging

This section will help you to generate executable DNSTester for debugging. For doing this, you need to install two different packages on your computer, and finally, you will be able to build the DNSTester. You need to install the picottcn TTCN-3 compiler and the cdgen CoDec Generator . You can find the two required scripts. The installation for the picottcn compiler is in the Go4IT/package2/build folder. The other, for building the cdgen is in the Go4IT/package2/cdgen/t3devkit folder.

How to

Install picottcn

Firstly, you have to run ./autogen.sh in Go4IT/package2/build folder. And then use ./configure command to generate the makefiles. Meanwhile, you can use the --prefix with the .configure command to change the target directory for the installation, for example ./configure --prefix=$(installation path). Using this modifier, it is possible to customize the installation directory to one different from the standard one (/usr/local). After that, you have to execute make && make install.

   cd Go4IT/package2/build
   ./autogen.sh
   ./configure
   make
   make install

Install cdgen

Secondly, you run ./autogen.sh in Go4IT/package2/cdgen/t3devkit folder. And you should use command export PATH = $(installation path)/bin:$PATH to add the directory of excutable picottcn to the linux path. Then, you use ./configure command to generate makefiles. Similarly, you can use the --prefix with the .configure command to change the target directory for the installation. After that, you have to make && make install.

   cd Go4IT/package2/cdgen/t3devkit
   ./autogen.sh
   ./configure
   make
   make install

Build DNSTester

Last, you run make in Go4IT/package2/cdgen/t3devkit/examples/DNSTester folder. And now you can have executable DNSTester in this folder.

   cd Go4IT/package2/cdgen/t3devkit/examples/DNSTester 
   make

Enjoy!

   ./DNSTester

JVM

Graphical interface requires JVM 1.6. Even though during configuration phase only a warning is issued when older JVM is found, this should be considered an error when running the package 2 executable. Compilation is allowed for other usages of package 2 compilation (i.e. picoTTCN compiler or CDGen tool). If you are interested in execution of package 2, then you need JVM 1.6.

--prefix

It might be useful to change the target directory for the installation using the --prefix with the .configure command. Using this modifier, it is possible to customize the installation directory to one different from the standard one (/usr/local).

Tested platforms

Reported (known) list of distros where we were [not] able to build and install the package2. Required components are the standard ones of the distribution, not ones that we installed manually. If you install them manually, maybe you will get different results.

Known to work

• OpenSuSE 10.2 (arch i586)
• OpenSuSE 10.3 (arch x86_64)
• Ubuntu 7.10

Known to have problems

• Fedora Core 6
• Fedora Core 5