Ubuntu 8.x and 9.x

Ubuntu home page: http://www.ubuntu.com

Ubuntu Linux Installation Hints:

• Packages: in addition to default suggestions and your choices,
  
• choose "Desktop" or "Server" for the installation type
• VFS6 only: when the default installation finishes, install package "libstdc++5" via System → Administration → Synaptic Package Manager, otherwise VFS would report at linking stage "/usr/bin/ld: warning: libstdc++.so.5, needed by /usr/local/FlagShip6/lib/libFlagShip6.so, not found"
• for running executables in Terminal i/o mode using "newfswin" script, you will also need to install the "tcsh" package
• to be able to create statically linked executables, install packages "libxext-dev", "libsm-dev", "libstdc++6-4.*-dev" and "libjpeg62-dev"
   
• For 64-bit Ubuntu distribution, you will additionally need standard packages "ia32-libs", "gcc-4.x-multilib" and "g++-4.x-multilib" (where 4.x corresponds to your installed gcc, e.g. 4.3). For VFS6, install also the "lib32stdc++5" package, e.g. from https://launchpad.net/ubuntu/warty/amd64/lib32stdc++5/
• In the /usr/local/FlagShip7/FS7config file (or in /usr/local/FlagShip6/FS6config for VFS6), disable MACRO1:... by # in front, and enable the following MACRO1:... line containing -L/usr/lib32 entry.
• VFS6 only: in the same FS6config file, add -m32 to CCNAME : ... line
• See also this 64bit info for further requirements.
   
• Running Ubuntu as Guast in VmWare6 is supported, but the GUI display is slower than in native mode. Terminal i/o mode is also ok, use "newfswin applic [-io=t]" from KDE or Gnome console for VFS applications.

Installation of Visual FlagShip 7.1.* (VFS7):

• Install the tar (non-rpm) based package FlagShip-7*.tgz, see the booklet for details and step-by-step instruction
• The main FlagShip directory is /usr/local/FlagShip7
• The "libstdc++.so.5" library is not required anymore
• Ubuntu supply all required static libraries in packages suggested above, so you may compile both dynamically (default) and statically (using the -stat compiler switch). If you get get some warnings at the end of FlagShip installation, or linker errors at static linking, post-install the required packages noted above from the Ubuntu distribution.

Installation of Visual FlagShip 6.1.* (VFS6):

• Create empty directory of your choice (e.g. mkdir /tmp/fsinstall ; cd /tmp/fsinstall), download the tar-based media file (wget http://www.fship.com/download/fs6linux-kernel26-tar_pdf.tgz) and un-tar it (tar xvzf fs6linux-kernel26-tar_pdf.tgz), read the INSTALL file (less INSTALL ). Here extract from in short:
  cd /usr/local ; sudo tar xvzf /tmp/fsinstall/FlagShip-6*_linux26.tgz ; cd FlagShip6 ; sudo FS6install
• The main FlagShip directory is user selectable, standard is /usr/local/FlagShip6

Using FlagShip:

• In VFS7, read the short step-by-step instruction for using FlagShip in the booklet (available also in the main /usr/local/FlagShip7 directory)
• If in X/GUI environment (KDE, Gnome etc): open console/terminal window.
• To test and run supplied examples, invoke  cd /usr/local/FlagShip6/examples ; make
• VFS6 only: If you get message "libstdc++.so.5, needed by /usr/local/FlagShip6/lib/libFlagShip6.so, not found" at the time of linking or executing the application, you will need to install "libstdc++5" package, see above .
• Compile your sources as described in fsman section FSC, e.g. "FlagShip myapp*.prg", a short help is available via "FlagShip -h". Note the case sensitive names in Unix/Linux.
• Watch for displayed compiler and linker errors, and fix if any.
• If everything is ok, execute (see fsman section FSC):
  ./a.out            # in GUI mode
  ./a.out -io=t      # in Textual i/o mode, preferably with "Terminal → Character Encoding → Western (IBM850)"
  newfswin ./a.out   # alternative for Textual i/o mode in X11 environment
• In some Ubuntu packages, you may need to disable line 416 (#xrdb -merge ...) and enable line 419 (source $FlagShipDir/bin/$xmapFile) in /usr/local/FlagShip6/bin/newfswin to proper support Terminal i/o in X11 environment.
• The on-line manual is available by entering "fsman &" in KDE/Gnome console for GUI mode, or "newfswin fsman" for textual mode. Manual in pdf format is available in /usr/local/FlagShip[6,7]/manual or in Web. Printed manual is available upon request.
• Step-by-step instruction for converting available applications to GUI is given in fsman section LNG.9.6
• Examples are available in /usr/local/FlagShip[6,7]/examples and .../tools directory. Best to copy them to your working directory.
• On problems or questions, please check the on-line manual and FAQ first. If your problem persist, contact FlagShip support - we grant free tech support not only for the licensed, but also for the Test/Eval version.

Known Issues :

• If the PC-8 semi-graphic characters are displayed in textual mode as Ä's (A-umlaut) etc, you may either
  - start the application via newfswin, newfscons or newfsterm (see above and Release Notes in fsman) which automatically sets the proper environment, or
  - disable Unicode i.e. set the environment variable "LANG=en_EN", and start the application via newfswin
  See also and/or test with /usr/local/FlagShip6/examples/boxcommand.prg
• If the last character in the manual pages seems to be missing in GUI mode, select Courier[adobe] via Menu→Options→Font→Input/Output or assign other font via command-line parameter, see fsman -h for furtehr details.

Additional Info:

Since FlagShip translates the Xbase code to C code as an intermediate step and requires object compatible libs during the linking stage, C compilers, utilities and libraries must be chosen with great care, otherwise upredictable errors may occur.

The C compiler (and the optional static libs) is required only in the developing phase, it is not required for the user of your application, which only needs the by FlagShip produced executable (i.e. your own application executables, see also fsman section SYS.1.2 for distribution hints).