7.3. Preparation

First step is to download and install all software pointed out in Section 7.1 and Section 7.2.

7.3.1. Creating user and group

V-q daemons can work as any user, but it is suggested to run them under _vq group and _vq user.


For security reasons you should not run it as root. It's better to prevent than cure.

You can use following commands to create this account (works under Linux and OpenBSD):

groupadd _vq
useradd -g _vq -d /var/vq _vq

7.3.2. Unpacking sources

Depending on package format you can use tar, bzip2, gzip to decompress archive.

If archive's name ends with .tar.gz you can unpack it with following commands:

tar -xzvf v-q.*.tar.gz

If you tar doesn't supports gzip unpacking use:

gzip -dc v-q.*.tar.gz | tar -xvf -

If archive's name ends with .tar.bz2 you can unpack it using:

bzip2 -cd v-q.*.tar.bz2 | tar -xvf -

At this time sources are released only with specified formats.

Note: Bzip2 gives better compression rate than gzip but it's not as popular as gzip so before downloading archive in this format check if you have it installed on your system.

7.3.3. Configuration before compilation

Before running make you must configure sources. There's no configure script. V-q don't use autoconf and it's family.

But don't be scared. Configuration is quite easy - all you need to do is edit few files.

First you need to set compiler and its options. In the main directory there are following files:

If you use other options or programs to compile your version of v-q please send information about them to Paweł Niewiadomski

Next step is to edit files with extensions: .inc and .lib. First are used during compilation, they include informations about directories used in searching for included files. Second are used while linking, they include references to libraries. Selecting CORBA implementation

Before compilation you're able to select CORBA implementation v-q should use. If you want to use other than default you need to modify 3 files.

corba.lib should include all arguments for make-so that will configure linker. This means that you should put there arguments specifying all libraries used by CORBA implementation.

corba.inc should include arguments for comp-so and compile that will tell compiler about include files needed by CORBA implementation. It also need to include argument telling which implementation should be used. For example to use MICO you should add -DP_USE_MICO. This means that P_USE_MICO will be defined during compilation. Other available options:

  • P_USE_MICO - for MICO

  • P_USE_OMNIORB - for omniORB

  • P_USE_ORBACUS - for Orbacus

  • P_USE_TAO - for TAO

  • P_USE_ORBIX - for Orbix

Note: This software was tested only with MICO (threads disabled) and omniORB.

Last thing that must be changed is an IDL translator definition - file idl includes command that is used to translate IDL files into C++. This file includes examples for various CORBA implementations.

Example 7-1. corba.inc for MICO installed in /usr/local/progs/mico

-DP_USE_MICO -I/usr/local/progs/mico/include

Example 7-2. corba.lib for MICO installed in /usr/local/progs/mico

-L/usr/local/progs/mico/lib -lmicocoss2.3.11 -lmico2.3.11 -lssl -lcrypto

Example 7-3. corba.inc for omniORB installed in /usr/local/progs/omniorb

-DP_USE_OMNIORB -I/usr/local/progs/omniorb/include

Example 7-4. corba.lib for omniORB installed in /usr/local/progs/omniorb

-L/usr/local/progs/omniorb/lib -lCOS4 -lCOSDynamic4 -lomniORB4 -lssl -lcrypto -lpthread 
Hosted by: BerliOS Logo SourceForge.net Logo