S A N K H Y A

Copyright (c) 2002 Sankhya Technologies Private Limited.
All rights reserved.

SANKHYA Varadhi: Development Notes for using SANKHYA Varadhi for QNX
====================================================================

   SANKHYA Varadhi has been ported to QNX Neutrino OS. It supports the 
   self-hosted x86 target environment. Applications can be developed using 
   SANKHYA Varadhi for QNX x86 target using QNX SDK (g++ 2.95.3).

   SANKHYA Varadhi is supported as a cross-platform development environment 
   for QNX. The development tools are not yet available for QNX native.
   SANKHYA Varadhi applications for QNX targets are built on the host 
   system (e.g. Solaris) and executed on QNX target OS.

Pre-requisites

   QNX Neutrino 6.2.0 OS environment and QNX Momentics Development Tools 
   environment should be setup before using SANKHYA Varadhi. Path to 'qcc'
   should be added to PATH variable before using SANKHYA Varadhi for
   creating Varadhi platforms and developing applications. 

   Refer to QNX documentation for setting up QNX environments.

   a. QNX Neutrino OS for x86

      Host      : Sun Sparc
      Host OS   : Solaris 7/8
      Target    : x86
      Target OS : QNX Neutrino OS 6.1.0 / 6.2.0
      Tools     : QNX SDK (g++ 2.95.3)

      Note:

         Since SANKHYA Varadhi development tools are not available for QNX 
         native, self-hosted development on QNX Neutrino OS is not supported.
         It requires the Varadhi platform and IDL stub and skeleton code to be
         generated in the host system (e.g. Solaris) and then copied over to
         QNX host for building and executing.

Using Varadhi for QNX:

   Varadhi is ported to work on QNX Neutrino OS environment. QNX TCP/IP 
   stack (npm-tcpip suite) is used as the Transport Layer.

   Refer to the main samples README in $VARADHI/samples directory
   ( %VARADHI%\samples on Windows host ) to setup Varadhi Target Platform,
   to build and execute the demos. The steps mentioned in the README file
   are same for QNX except (3) "Create a Varadhi Target Platform" and 
   (7) "Running the demo program". Refer below for creating a Varadhi Target 
   Platform for QNX and to run the demo program under QNX.


   1. Create a Varadhi Target Platform for QNX OS for x86.
 
      Varadhi can be customized for a particular target configuration using
      vconf. On Unix, Varadhi configuration files are provided under
      $VARADHI/etc/config directory to create various Varadhi Target Platforms.
      On Windows NT/2000 host, the location is %VARADHI%\etc\config directory.

      For example, to create a default platform on Solaris host for x86 QNX,
      that supports C++ Exception, use the following.

      1.a    Change directory to your workspace.

             In csh

                % cd $WORK_DIR

      1.b    Invoke vconf with three config files, one providing configuration
             options for the ORB, another one specifying the target platform
             (x86 QNX using GNU g++) and another one for licensing.

             In csh

                % vconf defaults x86-gcc-qnx license

             The configuration that is built with 'defaults' configuration
             file enables C++ Exception support.  

   2. Running the demo program

      Copy the executables (for e.g., 'server' and 'client' for adder demo) to 
      QNX Neutrino OS (self-hosted x86) environment.

      For example, to run the adder demo, start the 'server' application and
      then run the 'client' application.

      a. Start the Server Application

         In sh

            % ./server &

      b. Run the Client Application

         In sh

            % ./client   

      To run other demo programs, follow the steps mentioned in the README
      files in the individual demo directory. The README files in the 
      individual demo directory uses 'csh' as example. Applications can be
      invoked similarly in QNX shell.

      Note:

          'server' and 'client' are not required to be run on the same host. If
          different hosts are used, copy the IOR files created by the server
          applications to the client host under the same demo location.