Fedora Core 3, 4, 5

Fedora Core home page: http://fedora.redhat.com

Linux Installation Hints:

• Packages: in addition to default suggestions and your choices,
  - enable "Developmnent Tools" or post-install gcc
  - enable "X Software Development" (for static libs)
  - enable "KDE" (suggested, not strictly required)
  - enable "Editors" (suggested for several programmers editors)
   
• Running Fedora as Guast in VmWare5 is supported, but the GUI display is significantly 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 6.1.4:

• Install the .rpm based package FlagShip-6.1-43.i386.rpm, see INSTALL file in the distribution ("less INSTALL" ) for details
• The main FlagShip directory is /usr/local/FlagShip6
• Fedora 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 package from Fedora CD-ROM or DVD distribution.

Using FlagShip:

• If in X/GUI environment (KDE, Gnome etc): open console/terminal window.
• 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. The displayed gcc 3.4 warning "cc1: note: -fwritable-strings is deprecated; see documentation for details" is harmless and can be ignored.
• If everything is ok, execute (see fsman section FSC):
  ./a.out            # in GUI mode
  newfswin ./a.out   # for Textual i/o mode in X11 environment
• The on-line manual is available by entering "fsman &" in KDE/Gnome console for GUI mode, or "newfswin fsman -io=t" for textual mode. 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/FlagShip6/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 eiter 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).