README.PC 4.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109
  1. Midnight Commander for Win32 and OS/2
  2. -------------------------------------
  3. 0. Introduction
  4. 1. Compiling
  5. 2. Changes made
  6. 3. Authors and maintainers
  7. 0. Introduction
  8. ---------------
  9. Yes, Midnight Commander can be compiled for Win32 (Microsoft Windows 95, 98 and
  10. NT) and OS/2. It has many bugs, but is quite stable now. Maybe you can help as
  11. a beta tester or as a programmer. In either case you would like subscribe to
  12. mc-devel list (see readme files in main doc on how to do this) and contact us.
  13. Please note, that Midnight Commander remains primarily a file manager for
  14. UNIX-like systems, so recent changes may occasionally break something.
  15. You should not expect that it will work on your system better than file
  16. managers written natively for your OS.
  17. 1. Compiling
  18. ------------
  19. 1.1. Compiler
  20. -------------
  21. If you really want to enjoy free software under your non-free OS, you should
  22. try free compilers. Three of them are supported: EMX (OS/2), RSX and Mingw32
  23. (Win32). RSX is based on EMX, and can also cross-compile for OS/2 under
  24. Windows. Mingw32 is concieved as a free clone for Microsoft Visual C++.
  25. Please note, that all above compiler are based on GCC (GNU C compiler), but
  26. use different libraries.
  27. CygWin32 is not (yet) powerful enough to compile Windows-specipic portion of
  28. the Midnight Commander, but you may try to compile MC using UNIX configuration
  29. files. As you can easily imagine, resulting binary will need termcap or
  30. terminfo and use ANSI-sequences for output which is probably not what you want.
  31. You may also try non-free compilers. Microsoft Visual C++ (4.0 and above),
  32. Borland C++ (both for Win32 and OS/2) and IBC CSet are supported. "Supported"
  33. means merely that there are specific makefiles for those compilers, but it
  34. does not even assume that you will compile MC using them out-of-box.
  35. 1.2. General issues
  36. -------------------
  37. See pc/README, pc/BUGS, pc/TODO for the information concerning current state
  38. of the port.
  39. You may need to create some fake includes to compile. You may also need to
  40. change something in the MC sources.
  41. 1.3 Windowing Library
  42. ---------------------
  43. Currently only support for SLang windowing library is given. There are
  44. curses clones ported to Win32 and OS/2, but I believe that since there is
  45. no analogs for autoconf for those systems, we should avoid unnecessary
  46. difficulties.
  47. Currently the PC port SLang included in this distribution (see slang/
  48. subdirectory). This is a subset of SLang 0.99.38 distribution with some
  49. bugs fixed. There are also MC-specific changes in the code.
  50. SLang 0.99.38 has problems with OS/2 if you like console with more than
  51. 80x25 characters. You may try to use a newer SLang. It is possible, but it
  52. is also quite tricky.
  53. 1.4 Features and Limitations
  54. ----------------------------
  55. Internal editor is supported (including syntax highlighting).
  56. VFS (virtual file system) is not supported.
  57. X11 ports are not supported.
  58. 2. Changes made
  59. ---------------
  60. 2.1. Changes to main code
  61. -------------------------
  62. Changes in the main code are enclosed in #ifdef _OS_NT, __os2__ or OS2_NT
  63. blocks.
  64. In some cases we supressed code. This is temporal (so that mc can compile). In
  65. the future we will provide fake or true interfaces for these features.
  66. - Links: creation and information on links are not supported. We
  67. should provide a fake interface for the local filesystem and
  68. a true one for networked.
  69. - GID/UID queries (get_user, owner, preserve UID/GID on copy, ...).
  70. - TERMinals: all the code directly done with terminals must be supressed.
  71. - Signals: deleted. Should support the native ones.
  72. - pipes: had some trouble in ext.c and with error_pipes but soon will be
  73. fixed.
  74. - Chown command: Not supported yet.
  75. 2.2. Files rewritten
  76. --------------------
  77. There are several files with so many changes that they have been moved to pc/
  78. subdirectory. Some of them are common for Win32 and OS/2, some of them are
  79. system-specific. System-specific files bear a clear mark in their names
  80. (for example, dirent_nt.c)
  81. Our intension should be, however, to make most code system-independent. This
  82. would increase code reuseabilibity and maintainability :-)
  83. See pc/ subdirectory for further details.
  84. 3. Authors and maintainers
  85. --------------------------
  86. This port is based on the port for Windows NT by
  87. Juan Grigera <grigera@isis.unlp.edu.ar>
  88. and the port for OS/2 by
  89. Alexander Dong <ado@software-ag.de>
  90. Both ports were merged to one PC port by me,
  91. Pavel Roskin <pavel_roskin@geocities.com>
  92. Please note, that I'm using Linux now. I have access to Windows 95 machines,
  93. but I have no access to OS/2 machines. If you are really keen to continue my
  94. work, please drop me a letter.
  95. Pavel Roskin <pavel_roskin@geocities.com>