README 4.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889
  1. Tue Aug 20 16:19:51 CDT 1996
  2. Andy Fingerhut (jaf@arl.wustl.edu)
  3. In release 1.4, there are quite a few hand modifications to the C code
  4. that was automatically created from the Fortran code with f2c. They
  5. are all summarized in change log comments at the beginning of the
  6. changed files. All of the original files from f2c were checked in to
  7. RCS before modification, so it is possible to see exactly what changes
  8. were made, for the extremely curious. That precaution was also for my
  9. benefit, in case I ever recompile the Fortran sources, and want to
  10. make similar changes to that new C source code.
  11. Below is the README file for this directory included with the 1.3
  12. release of the LPC-10 package. A few parts of it are a little out of
  13. date, but it is correct for the most part.
  14. Sun Jul 7 15:30:31 CDT 1996
  15. Andy Fingerhut (jaf@arl.wustl.edu)
  16. To create the LPC-10 library, copy the appropriate makefile to the
  17. proper name for easy use, e.g., for Unix, copy makefile.unx to the
  18. file "Makefile". The file makefile.dos has been used with some
  19. version of the 'nmake' utility that comes with the Microsoft C
  20. compiler (the same one used for Nautilus v1.5a, which I believe
  21. specifies Microsoft C version 7.0 or later).
  22. Then edit the file lpc10.h in the directory above. It should already
  23. be set up to work properly on any Unix compiler for which "int" is 32
  24. bits and "short" is 16 bits, and under the Microsoft C compiler
  25. configured so that "long" is 32 bits and "int" is 16 bits. There must
  26. be a typedef for the two types INT32 and INT16 in that file. You
  27. should choose types that compile to those sizes using your compiler,
  28. because there are places in the LPC-10 code that expect INT16's to
  29. have exactly 16 bits (at least, I *think* they must be no larger), and
  30. INT32's to have exactly 32 bits.
  31. A few notes on how these files were created
  32. -------------------------------------------
  33. (This section is mostly for my benefit, so I can remember what I did.
  34. You don't need to read it if you just want to use this package. It
  35. might be useful to read it if you change the Fortran sources and want
  36. to recreate a usable library of C sources. -- Andy)
  37. These C sources were created automatically from the Fortran sources
  38. using f2c, for the most part. Listed below are the extra
  39. modifications that were made after this automatic conversion. Many of
  40. them were made so that it was not necessary to install f2c in order to
  41. use this LPC-10 coder.
  42. 1.
  43. Put all of those files that were necessary for only the coder, rather
  44. than an application that uses the coder, into this subdirectory called
  45. lpc10.
  46. 2.
  47. Copied f2c.h from the f2c distribution into this subdirectory. Some
  48. modifications were made to the "typedef" statements in this file, to
  49. explicitly indicate the sizes (in bits) that different integer types
  50. should be. The types INT32 and INT16 must be defined in a file called
  51. lpc10.h in the directory above. Created the file f2clib.c, containing
  52. only the functions pow_ii(), r_sign(), and i_nint() from the f2c
  53. library.
  54. 3.
  55. The f2c output originally had a file called contrl_com.c, that defined
  56. a small structure containing a few variables that were used in many
  57. different functions of the LPC10 code. Every file containing
  58. functions that used it defined it as "extern", while contrl_com.c
  59. actually allocated storage for the structure. Bill Dorsey, one of the
  60. lead developers of Nautilus, said that the Microsoft C compiler had
  61. problems either compiling this file, or linking it with all of the
  62. other compiled files, so he just eliminated that file and removed the
  63. "extern" keyword from the one of the files that declared it that way.
  64. The file chosen (arbitrarily) was analys.c.
  65. 4.
  66. Copied the makefiles for Unix and Microsoft C from the Nautilus v1.5a
  67. distribution into the lpc10 directory. Modified them to take out
  68. references to Nautilus. These makefiles don't create an executable,
  69. but a library of compiled functions called liblpc10.a (Unix) or
  70. LPC10.LIB (DOS). This library can be used when linking an executable
  71. that calls the functions lpcini_(), lpcenc_(), and lpcdec_().