README.PC 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103
  1. GNU Midnight Commander for Win32
  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 (all versions of
  10. Microsoft Windows starting with Windows 95 for all platforms, except
  11. Windows CE). It may be tricky to compile, it may be buggy, but it should
  12. be usable. Maybe you can help as a beta tester or as a programmer.
  13. In either case you would like subscribe to the mc-devel list (see README
  14. and FAQ) and contact us.
  15. Please note that Midnight Commander remains primarily a file manager for
  16. UNIX-like systems. You should not expect that it will work on your
  17. system better than a file manager written specifically for your OS.
  18. 1. Compiling
  19. ------------
  20. 1.1. Compiler
  21. -------------
  22. If you really want to enjoy free software under your non-free OS,
  23. you should try free compilers. Two of them are supported: RSXNT and
  24. MinGW. Please visit their respective sites for more information.
  25. RSXNT: http://www.mathematik.uni-bielefeld.de/~rainer/
  26. MinGW: http://www.mingw.org/
  27. MinGW is also included with Cygwin (http://www.cygwin.com/).
  28. Cygwin envirinment is so close to UNIX, that it's possible to compile
  29. GNU Midnight Commander in the same way as it's done in UNIX (see file
  30. INSTALL for details). However, you should realize that you would get a
  31. UNIX program that has no idea about drives, Windows-style permissions
  32. and some other Windows-specific features. This is not the Win32 port
  33. discussed in this document.
  34. Skeaking of non-free compilers, Microsoft Visual C++ (4.0 and above) and
  35. Borland C++ are supported. "Supported" means merely that there are
  36. specific makefiles for those compilers, but it does not even assume that
  37. you will compile GNU Midnight Commander out-of-box.
  38. 1.2. General issues
  39. -------------------
  40. See pc/README, pc/BUGS, pc/TODO for the information concerning current
  41. state of the port. You may need to hack the code in order to compile it.
  42. 1.3 Windowing Library
  43. ---------------------
  44. Currently only support for the S-Lang windowing library is provided.
  45. There are curses clones ported to Win32, but I believe that since we
  46. are not using autoconf for the Win32 port, we should avoid unnecessary
  47. difficulties.
  48. Currently the Win32 port only can use S-Lang included in this
  49. distribution (see slang/ subdirectory). This is a subset of S-Lang
  50. 0.99.38 distribution with some bugfixes and MC-specific code changes.
  51. 1.4 Features and Limitations
  52. ----------------------------
  53. Internal editor is supported (including syntax highlighting).
  54. Internal viewer is supported (including hex editor).
  55. VFS (virtual file system) is not supported.
  56. Concurrent subshell is not supported.
  57. 2. Changes made
  58. ---------------
  59. 2.1. Changes to main code
  60. -------------------------
  61. Changes in the main code are enclosed in #ifdef NATIVE_WIN32 blocks.
  62. In some cases we suppressed code. This is temporal (so that mc can compile).
  63. In the future we will provide fake or true interfaces for these features.
  64. - Links: creation and information on links are not supported. We
  65. should provide a fake interface for the local filesystem and
  66. a true one for networked.
  67. - GID/UID queries (get_user, owner, preserve UID/GID on copy, ...).
  68. - TERMinals: all the code directly done with terminals must be suppressed.
  69. - Signals: deleted. Should support the native ones.
  70. - pipes: had some trouble in ext.c and with error_pipes but soon will be
  71. fixed.
  72. - Chown command: Not supported yet.
  73. 2.2. Files rewritten
  74. --------------------
  75. There are several files with so many changes that they have been moved
  76. to pc/ subdirectory. Our intention should be, however, to make most code
  77. system-independent. This would increase code reuse and maintainability.
  78. See pc/ subdirectory for further details.
  79. 3. Authors and maintainers
  80. --------------------------
  81. This port is based on the port for Windows NT by
  82. Juan Grigera <grigera@isis.unlp.edu.ar>
  83. The code is not actively maintained, but the patches are applied.
  84. Please send your changes to the mc-devel list.