README400 1.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. ZLIB version 1.2.11 for OS/400 installation instructions
  2. 1) Download and unpack the zlib tarball to some IFS directory.
  3. (i.e.: /path/to/the/zlib/ifs/source/directory)
  4. If the installed IFS command suppors gzip format, this is straightforward,
  5. else you have to unpack first to some directory on a system supporting it,
  6. then move the whole directory to the IFS via the network (via SMB or FTP).
  7. 2) Edit the configuration parameters in the compilation script.
  8. EDTF STMF('/path/to/the/zlib/ifs/source/directory/os400/make.sh')
  9. Tune the parameters according to your needs if not matching the defaults.
  10. Save the file and exit after edition.
  11. 3) Enter qshell, then work in the zlib OS/400 specific directory.
  12. QSH
  13. cd /path/to/the/zlib/ifs/source/directory/os400
  14. 4) Compile and install
  15. sh make.sh
  16. The script will:
  17. - create the libraries, objects and IFS directories for the zlib environment,
  18. - compile all modules,
  19. - create a service program,
  20. - create a static and a dynamic binding directory,
  21. - install header files for C/C++ and for ILE/RPG, both for compilation in
  22. DB2 and IFS environments.
  23. That's all.
  24. Notes: For OS/400 ILE RPG programmers, a /copy member defining the ZLIB
  25. API prototypes for ILE RPG can be found in ZLIB/H(ZLIB.INC).
  26. In the ILE environment, the same definitions are available from
  27. file zlib.inc located in the same IFS include directory as the
  28. C/C++ header files.
  29. Please read comments in this member for more information.
  30. Remember that most foreign textual data are ASCII coded: this
  31. implementation does not handle conversion from/to ASCII, so
  32. text data code conversions must be done explicitely.
  33. Mainly for the reason above, always open zipped files in binary mode.