suite3270 Build and Install Instructions
Building on Unix or Cygwin
To build the entire 3270 emulation suite, including native Unix
programs and cross-compiled Windows programs, use:
To install Unix binaries in the default install directory
To install Unix manual pages, use:
To remove intermediate files, use:
To remove all derived files, use:
Object files will be placed in directories named
obj/architecture. For example, 64-bit Linux object
files are placed in obj/x86_64-unknown-gnu-linux. 32-bit
Windows object files are placed in obj/win32. 64-bit Windows
object files are placed in obj/win64.
If you only want to build a subset of the programs, you can limit the
scope of the configure script with the following options. Note that the
options are cumulative, so you can specify exactly the set of programs
When you limit the configuration this way, it changes the top-level
make targets, so make, make install,
make clean and make clobber will
operate only on the programs you have configured.
||Include all of the Unix programs
||Include all of the Windows programs
Summary of Common configure Options
The top-level configure script accepts the following
options. Note that these apply only to Unix; the options for Windows
programs are fixed.
There are also configure options that are specific to
individual programs. These can be passed to the top-level
configure script. See each individual program's additional
build information for details.
||Print a help message.
||Install architecture-independent files under
prefix (defaults to /usr/local)
||Install architecture-dependent files (executables) under
eprefix (defaults to same as prefix)
||Install user executables dir (defaults to
||Install configuration files (ibm_hosts,
character sets) in dir (defaults to
||Leave out APL character support.
||Leave out DBCS (Double Byte Character Set)
||Leave out local process (connecting to
"-e shell_command") support.
This will be automatically disabled if the local system
does not support the forkpty() library call.
||Leave out SSL (Secure Sockets Layer)
support. SSL support requires the OpenSSL library.
||Specify the directory where the OpenSSL
library is installed.
Selective Build Targets
To build just the Unix programs, use:
To cross-compile just the Windows programs, use:
To build an individual program, such as s3270, just make it:
Each of the top-level symbolic targets can be limited to a group
(unix or windows) or to a program, by adding the desired prefix:
Notes for Cygwin
The minimum set of extra Cygwin packages needed to build the 3270 suite
To cross-compile native Windows binaries, you need this package:
- The make package from the Devel group
- The gcc-core package from the Devel group
- For SSL support, the openssl-devel package from
the Devel group
Other packages are needed by the specific programs, and are listed in those
programs' build instructions.
- mingw-w64-gcc from the Devel group
Notes for Mac OS X
Everything except x3270 is built the usual (Unix) way on Mac OS X.
But to build x3270, you first need to install XQuartz (http://xquartz.macosforge.org/).
Then to build all of the emulators, use the following commands:
./configure --enable-unix --x-includes=/opt/X11/include
Notes for Solaris 2.x and Sun's C Compiler
Do not use Sun's BSD-compatibility compiler, /usr/ucb/cc. This
is good advice in general, but in particular, the 3270 suite will not build
with it. You should have a directory containing gcc (recommended)
or Sun's standard compiler in your $PATH ahead of /usr/ucb.
Building on FreeBSD
FreeBSD's iconv library is installed in /usr/local, so
the the following options must be passed to the configure script:
./configure LDFLAGS=-L/usr/local/lib CPPFLAGS=-I/usr/local/include
Building with Visual Studio 2013
Visual Studio GUI
The Visual Studio solution is called suite3270.sln in the
VS2013 folder. There are individual projects for each of the
programs and components. The Debug and Release configurations build
code without OpenSSL support. The SSL-Debug and SSL-Release
configurations build code with OpenSSL support, and require standard
OpenSSL header files to be installed in the folder
Visual Studio Command Line
To build with Microsoft Visual Studio from the command prompt, first
open a command console with Visual Studio build environment variables
set. Switch to the VS2013 directory, and type:
The usual msbuild options are available, such as /m,
/p:Configuration (which can specify Debug, Release, SSL-Debug
or SSL-Release) and /p:Platform (which can specify x86 or x64).