To install the files
you will need a copy of the source archive,
the base utilities archive for your OS
and the font and bitmap resource archive.
Uncompress all files in the archive into
the directoy on your system where you want
the files to live (normally ~/scitech).
Once you have installed the files, you need to configure the makefile utilties
and tools to allow you to compile the libraries.
The first step to set up the compile environment is always to edit the set-vars
script files specific to your platform. This file contains two very important
variables that you need to ensure are set correctly. These are:
SCITECH - Points to
the location where you installed the files
SCITECH_LIB - Should be the same as the above
The SCITECH_LIB variable
is where files get copied to when you do
a 'dmake install', and is usually the same
as the SCITECH variable. However it can be
different if you wish the libraries to be
installed to a different path such as on
a shared file server for release builds.
You should also ensure that you set the MGL_ROOT environment variable, which
points to the location of where you installed the MGL files. This is a runtime
varaiable that is used by the MGL to find all font, bitmap, icon and cursor resource
files.
Then, you need to edit the bin\set-vars-linux.sh script file to reference
the location where you have installed the files, and the locations where all
your compilers are installed. See the comments in set-vars-linux.sh for more
information.
Note that the Linux version of set-vars uses the MGL_ROOT environment variable
to set the SCITECH and SCITECH_LIB variables. For the most part you can probably
just set the MGL_ROOT variable and then execute the set-vars-linux.sh shell script
from your default shell profile (i.e. .bash_profile etc).
Once you have the startup file configured, you then need to run the following
each time you start a command shell to enable the SciTech makefile utilities
(a good idea to put into your startup scripts):
The second script file
sets up the compiler configuration for your
default compiler. The line above sets up
for GNU C/C++ for Linux (eventually other
compilers will come to Linux, such a MetroWerks).
NOTE: In the above script code, you need to *source* the script files to ensure
the environment variables are exported to your regular shell. Hence, make sure
the leading '.' is included.
NOTE: If you are developing on an older libc5 based system (as opposed to the
newer glibc as used by Red Hat 5.x, etc.), you will also need to set the LIBC=1
environment variable. This will tell our script files that you are running on
an older system and need to use the libc5 compiled binaries, and to put your
compiled libraries into the libc5 directories.
NOTE: In order to build the MGL libraries, you should have the latest Linux 2.x
kernel sources installed. The PM library depends upon a number of header files
from the 2.x kernels (joystick.h and mtrr.h) in order to build. You can build
for older kernels if you wish, but you will need to modify the PM library makefiles
to do this.
NOTE: In order to use the mouse and joystick under Linux, you will need to set
up the MGL mouse and joystick environment variables. See the section below on
Linux Rutime Setup for more information.
How to Compile the Libraries: Once you have all the startup scripts
configured and executed, you are ready to begin compiling.
Building all the SciTech MGL libraries in one fell
swoop is very easy. Simply change into the src directory
below where you have installed all the files and issue
a dmake build. i.e.
cd scitech/src
dmake build
Using 'dmake build' will force build
all the libraries. If any errors are encountered during
the build, it will stop and you can fix the errors
and then restart the build from the offending library
with a simple 'dmake' (i.e. the default target builds
for the selected compiler). You can also build each
library from each directory if you wish as well.
Also included are script files to build all libraries for your selected compiler
in both 'Debug' and 'Release' modes. To build the debug libraries, go into the
src directory and issue run the mkdebug script files. i.e.
cd scitech/src
mkdebug
To build the release libraries,
go into the src directory and issue run the mkrelease
script files. i.e.
cd scitech/src
mkrelease
All debug libraries end up under
the lib/debug directory tree, and all release libraries
end up under the lib/release directory tree. To link
your own programs with the debug libraries, you set
the environment variable CHECKED=1 (or set it on the
dmake command line). This will tell the dmake makefile
scripts to build in CHECKED mode (add extra runtime
checks) as to get the libraries from the lib/debug
directories. Otherwise the libraries are pulled from
the lib/release directory.
How to Compile the Sample Programs: Once you have all the libraries
built, you can compile the sample programs. To build
the example programs, go into the scitech/examples/mgl/samples
directory and run dmake to build all the example programs.
Linux Runtime Setup: In order for the MGL event libraries
to support the mouse in fullscreen console modes, we
need to directly interface to the installed mouse driver.
By default SciTech MGL will run without any mouse support
if the mouse environment variables have not been set
up. The MGL_MOUSEDRV environment varaiable should be
set to one of the following values, to inform SciTech
MGL what type of mouse you have:
MGL_MOUSEDRV =
GPM - Use the currently installed GPM driver
Microsoft - Microsoft and compatible serial mouse
PS2 - Microsoft and compatible PS/2 mouse
MouseSystems - Mouse Systems mouse
MMSeries - MMSeries mouse
Logitech - Logitech mouse
BusMouse - Microsoft bus mouse
MouseMan - MouseMan mouse
IntelliMouse - Microsoft Intellimouse
IntelliMousePS2 - Microsoft PS/2 Intellimouse
If you already have the standard
Linux GPM driver installed, you can set it to use
this driver by default.
NOTE: If any developers are familiar with mouse programming, we need someone
to modify the PM event library to auto-detect the installed mouse type. This
will then eliminate the need for users to configure the mouse environment variables
for MGL applications.
iNSTALLING
UNDER WINDOWS:
To install the files
you will need a copy of the source archive,
the base utilities archive for your OS
and the font and bitmap resource archive.
Uncompress all files in the archive into
the directoy on your system where you want
the files to live (normally c:\scitech).
Once you have installed the files, you need to configure the makefile utilties
and tools to allow you to compile the libraries.If you are compiling under DOS
in a Windows DOS box, you will need to set the environment for your DOS box to
at least 2048 bytes because SciTech MGL uses a lot of environment variables.
The first step to set up the compile environment is always to edit the set-vars
script files specific to your platform. This file contains two very important
variables that you need to ensure are set correctly. These are:
SCITECH - Points to
the location where you installed the files
SCITECH_LIB - Should be the same as the above
The SCITECH_LIB variable
is where files get copied to when you do
a 'dmake install', and is usually the same
as the SCITECH variable. However it can be
different if you wish the libraries to be
installed to a different path such as on
a shared file server for release builds.
You should also ensure that you set the MGL_ROOT environment variable, which
points to the location of where you installed the MGL files. This is a runtime
varaiable that is used by SciTech MGL to find all font, bitmap, icon and cursor
resource files.
Then, you need to edit the bin\set-vars.bat batch file to reference the
location where you have installed the files, and the locations where all your
compilers are installed. See the comments in set-vars.bat for more information.
Once you have the startup file configured, you then need to run the following
each time you start a command shell to enable the SciTech makefile utilities
(a good idea to put into your startup batch files):
The second batch file
sets up the compiler configuration for your
default compiler. The line above sets up
for Watcom C++ 11.0 32-bit DOS compilation.
Substitute this for any of the batch files
in the bin directory for the compiler you
are using.
How to Compile the Libraries: Once you have all the
startup scripts configured and executed,
you are ready to begin compiling. Building
all the SciTech MGL libraries in one fell
swoop is very easy. Simply change into the
src directory below where you have installed
all the files and issue a dmake build. i.e.
cd scitech\src
dmake build
Using 'dmake build' will
force build all the libraries. If any errors
are encountered during the build, it will
stop and you can fix the errors and then
restart the build from the offending library
with a simple 'dmake' (i.e. the default target
builds for the selected compiler). You can
also build each library from each directory
if you wish as well.
Also included are script files to build all libraries for your selected compiler
in both 'Debug' and 'Release' modes. To build the debug libraries, go into the
src directory and issue run the mkdebug script files. i.e.
cd scitech\src
mkdebug
To build the release libraries,
go into the src directory and issue run the
mkrelease script files. i.e.
cd scitech\src
mkrelease
NOTE: For DOS environments
without long filenames, the command for release
builds is 'mkreleas' without the traling
'e', because 'mkrelease' is longer than 8
characters. Both mkreleas.bat and mkrelease.bat
files are included.
All debug libraries end up under the lib\debug directory tree, and all release
libraries end up under the lib\release directory tree. To link your own programs
with the debug libraries, you set the environment variable CHECKED=1 (or set
it on the dmake command line). This will tell the dmake makefile scripts to build
in CHECKED mode (add extra runtime checks) as to get the libraries from the lib\debug
directories. Otherwise the libraries are pulled from the lib\release directory.
How to Compile the Sample Programs: Once you have all the libraries
built, you can compile the sample programs. To
build the example programs, go into the scitech\examples\mgl\samples
directory and run dmake to build all the example
programs.
iNSTALLING
UNDER OS/2:
To install the files
you will need a copy of the source archive,
the base utilities archive for your OS
and the font and bitmap resource archive.
Uncompress all files in the archive into
the directoy on your system where you want
the files to live (normally c:\scitech).
Once you have installed the files, you need to configure the makefile utilties
and tools to allow you to compile the libraries.
The first step to set up the compile environment is always to edit the set-vars
script files specific to your platform. This file contains two very important
variables that you need to ensure are set correctly. These are:
SCITECH - Points to
the location where you installed the files
SCITECH_LIB - Should be the same as the above
The SCITECH_LIB variable
is where files get copied to when you do
a 'dmake install', and is usually the same
as the SCITECH variable. However it can be
different if you wish the libraries to be
installed to a different path such as on
a shared file server for release builds.
You should also ensure that you set the MGL_ROOT environment variable, which
points to the location of where you installed the MGL files. This is a runtime
varaiable that is used by the MGL to find all font, bitmap, icon and cursor resource
files.
Then, you need to edit the bin-os2\set-vars.cmd script file to reference
the location where you have installed the files, and the locations where all
your compilers are installed. See the comments in set-vars.cmd for more information.
Once you have the startup file configured, you then need to run the following
each time you start a command shell to enable the SciTech makefile utilities
(a good idea to put into your startup batch files):
The second batch file
sets up the compiler configuration for your
default compiler. The line above sets up
for Watcom C++ 11.0 32-bit OS/2 compilation.
Substitute this for any of the batch files
in the bin directory for the compiler you
are using.
NOTE: In order for any of the OS/2 sample programs to run, you must have the
SDDHELP.SYS device driver loaded. Hence ensure you add this device driver to
your CONFIG.SYS file and then reboot in order to start using the MGL programs.
How to Compile the Libraries: Once you have all the startup
scripts configured and executed, you are ready
to begin compiling. Building all the SciTech MGL
libraries in one fell swoop is very easy. Simply
change into the src directory below where you have
installed all the files and issue a dmake build.
i.e.
cd scitech\src
dmake build
Using 'dmake build' will force
build all the libraries. If any errors are encountered
during the build, it will stop and you can fix
the errors and then restart the build from the
offending library with a simple 'dmake' (i.e. the
default target builds for the selected compiler).
You can also build each library from each directory
if you wish as well.
Also included are script files to build all libraries for your selected compiler
in both 'Debug' and 'Release' modes. To build the debug libraries, go into the
src directory and issue run the mkdebug script files. i.e.
cd scitech\src
mkdebug
To build the release libraries,
go into the src directory and issue run the mkrelease
script files. i.e.
cd scitech\src
mkrelease
NOTE: For DOS environments without
long filenames, the command for release builds
is 'mkreleas' without the traling 'e', because
'mkrelease' is longer than 8 characters. Both mkreleas.bat
and mkrelease.bat files are included.
All debug libraries end up under the lib\debug directory tree, and all release
libraries end up under the lib\release directory tree. To link your own programs
with the debug libraries, you set the environment variable CHECKED=1 (or set
it on the dmake command line). This will tell the dmake makefile scripts to build
in CHECKED mode (add extra runtime checks) as to get the libraries from the lib\debug
directories. Otherwise the libraries are pulled from the lib\release directory. How to Compile the Sample Programs: Once you have all the libraries
built, you can compile the sample programs. To
build the example programs, go into the scitech/examples/mgl/samples
directory and run dmake to build all the example
programs.
iNSTALLING
UNDER DOS:
To install the files
you will need a copy of the source archive,
the base utilities archive for your OS
and the font and bitmap resource archive.
Uncompress all files in the archive into
the directoy on your system where you want
the files to live (normally c:\scitech).
Once you have installed the files, you need to configure the makefile utilties
and tools to allow you to compile the libraries.If you are compiling under DOS
in a Windows DOS box, you will need to set the environment for your DOS box to
at least 2048 bytes because SciTech MGL uses a lot of environment variables.
The first step to set up the compile environment is always to edit the set-vars
script files specific to your platform. This file contains two very important
variables that you need to ensure are set correctly. These are:
SCITECH - Points to
the location where you installed the files
SCITECH_LIB - Should be the same as the above
The SCITECH_LIB variable
is where files get copied to when you do
a 'dmake install', and is usually the same
as the SCITECH variable. However it can be
different if you wish the libraries to be
installed to a different path such as on
a shared file server for release builds.
You should also ensure that you set the MGL_ROOT environment variable, which
points to the location of where you installed the MGL files. This is a runtime
varaiable that is used by SciTech MGL to find all font, bitmap, icon and cursor
resource files.
Then, you need to edit the bin\set-vars.bat batch file to reference the
location where you have installed the files, and the locations where all your
compilers are installed. See the comments in set-vars.bat for more information.
Once you have the startup file configured, you then need to run the following
each time you start a command shell to enable the SciTech makefile utilities
(a good idea to put into your startup batch files):
The second batch file
sets up the compiler configuration for your
default compiler. The line above sets up
for Watcom C++ 11.0 32-bit DOS compilation.
Substitute this for any of the batch files
in the bin directory for the compiler you
are using.
How to Compile the Libraries:
Once you have all the startup scripts configured and executed, you are ready
to begin compiling. Building all the SciTech MGL libraries in one fell swoop
is very easy. Simply change into the src directory below where you have installed
all the files and issue a dmake build. i.e.
cd scitech\src
dmake build
Using 'dmake build' will
force build all the libraries. If any errors
are encountered during the build, it will
stop and you can fix the errors and then
restart the build from the offending library
with a simple 'dmake' (i.e. the default target
builds for the selected compiler). You can
also build each library from each directory
if you wish as well.
Also included are script files to build all libraries for your selected compiler
in both 'Debug' and 'Release' modes. To build the debug libraries, go into the
src directory and issue run the mkdebug script files. i.e.
cd scitech\src
mkdebug
To build the release libraries,
go into the src directory and issue run the
mkrelease script files. i.e.
cd scitech\src
mkrelease
NOTE: For DOS environments
without long filenames, the command for release
builds is 'mkreleas' without the traling
'e', because 'mkrelease' is longer than 8
characters. Both mkreleas.bat and mkrelease.bat
files are included.
All debug libraries end up under the lib\debug directory tree, and all release
libraries end up under the lib\release directory tree. To link your own programs
with the debug libraries, you set the environment variable CHECKED=1 (or set
it on the dmake command line). This will tell the dmake makefile scripts to build
in CHECKED mode (add extra runtime checks) as to get the libraries from the lib\debug
directories. Otherwise the libraries are pulled from the lib\release directory.
How to Compile the Sample Programs: Once you have all the libraries
built, you can compile the sample programs. To
build the example programs, go into the scitech\examples\mgl\samples
directory and run dmake to build all the example
programs.
