From 922f8b75c32941e4b1958c6be06b85a4c9be8980 Mon Sep 17 00:00:00 2001 From: Pavel Roskin Date: Thu, 3 Jan 2002 08:27:25 +0000 Subject: [PATCH] * NEWS: Mention removal of the OS/2 port. * README.PC: Remove OS/2 specific parts. --- ChangeLog | 5 +++ NEWS | 1 + README.PC | 112 ++++++++++++++++++++++++++---------------------------- 3 files changed, 59 insertions(+), 59 deletions(-) diff --git a/ChangeLog b/ChangeLog index 51890719e..aa8d4ec7f 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2002-01-03 Pavel Roskin + + * NEWS: Mention removal of the OS/2 port. + * README.PC: Remove OS/2 specific parts. + 2002-01-02 Pavel Roskin * configure.in: Make help about --with-subshell easier to diff --git a/NEWS b/NEWS index 902ec3862..88ba1e73e 100644 --- a/NEWS +++ b/NEWS @@ -1,6 +1,7 @@ Yet to be released version 4.6. - GNOME edition has been removed. +- OS/2 port has been removed. - Large file support enabled by default. - Dropped support for the old Curses library. - Editor files are now stored in ~/.mc/cedit instead of ~/.cedit diff --git a/README.PC b/README.PC index 36809aa9a..81b97ac1a 100644 --- a/README.PC +++ b/README.PC @@ -1,6 +1,6 @@ -Midnight Commander for Win32 and OS/2 -------------------------------------- +GNU Midnight Commander for Win32 +-------------------------------- 0. Introduction 1. Compiling @@ -9,101 +9,95 @@ Midnight Commander for Win32 and OS/2 0. Introduction --------------- -Yes, Midnight Commander can be compiled for Win32 (Microsoft Windows 95, 98 and -NT) and OS/2. It has many bugs, but is quite stable now. Maybe you can help as -a beta tester or as a programmer. In either case you would like subscribe to -mc-devel list (see README files in main doc on how to do this) and contact us. -Please note, that Midnight Commander remains primarily a file manager for -UNIX-like systems, so recent changes may occasionally break something. -You should not expect that it will work on your system better than file -managers written specifically for your OS. +Yes, Midnight Commander can be compiled for Win32 (all versions of +Microsoft Windows starting with Windows 95 for all platforms, except +Windows CE). It may be tricky to compile, it may be buggy, but it should +be usable. Maybe you can help as a beta tester or as a programmer. +In either case you would like subscribe to the mc-devel list (see README +and FAQ) and contact us. + +Please note that Midnight Commander remains primarily a file manager for +UNIX-like systems. You should not expect that it will work on your +system better than a file manager written specifically for your OS. 1. Compiling ------------ 1.1. Compiler ------------- -If you really want to enjoy free software under your non-free OS, you should -try free compilers. Three of them are supported: EMX (OS/2), RSX and Mingw32 -(Win32). RSX is based on EMX, and can also cross-compile for OS/2 under -Windows. Mingw32 is conceived as a free clone for Microsoft Visual C++. -Please note, that all above compiler are based on gcc (GNU C compiler), but -use different libraries. -Cygwin is not (yet) powerful enough to compile Windows-specific portion of -the Midnight Commander, but you may try to compile MC using UNIX configuration -files. As you can easily imagine, resulting binary will need termcap or -terminfo and use ANSI-sequences for output which is probably not what you want. -You may also try non-free compilers. Microsoft Visual C++ (4.0 and above), -Borland C++ (both for Win32 and OS/2) and IBM CSet are supported. "Supported" -means merely that there are specific makefiles for those compilers, but it -does not even assume that you will compile MC by them out-of-box. +If you really want to enjoy free software under your non-free OS, +you should try free compilers. Two of them are supported: RSXNT and +MinGW. Please visit their respective sites for more information. + +RSXNT: http://www.mathematik.uni-bielefeld.de/~rainer/ +MinGW: http://www.mingw.org/ + +MinGW is also included with Cygwin (http://www.cygwin.com/). + +Cygwin envirinment is so close to UNIX, that it's possible to compile +GNU Midnight Commander in the same way as it's done in UNIX (see file +INSTALL for details). However, you should realize that you would get a +UNIX program that has no idea about drives, Windows-style permissions +and some other Windows-specific features. This is not the Win32 port +discussed in this document. + +Skeaking of non-free compilers, Microsoft Visual C++ (4.0 and above) and +Borland C++ are supported. "Supported" means merely that there are +specific makefiles for those compilers, but it does not even assume that +you will compile GNU Midnight Commander out-of-box. 1.2. General issues ------------------- -See pc/README, pc/BUGS, pc/TODO for the information concerning current state -of the port. -You may need to create some fake includes to compile. You may also need to -change something in the MC sources. +See pc/README, pc/BUGS, pc/TODO for the information concerning current +state of the port. You may need to hack the code in order to compile it. 1.3 Windowing Library --------------------- -Currently only support for SLang windowing library is given. There are -curses clones ported to Win32 and OS/2, but I believe that since there is -no analogs for autoconf for those systems, we should avoid unnecessary +Currently only support for the S-Lang windowing library is provided. +There are curses clones ported to Win32, but I believe that since we +are not using autoconf for the Win32 port, we should avoid unnecessary difficulties. -Currently the PC port SLang included in this distribution (see slang/ -subdirectory). This is a subset of SLang 0.99.38 distribution with some -bugs fixed. There are also MC-specific changes in the code. -SLang 0.99.38 has problems with OS/2 if you like console with more than -80x25 characters. You may try to use a newer SLang. It is possible, but it -is also quite tricky. + +Currently the Win32 port only can use S-Lang included in this +distribution (see slang/ subdirectory). This is a subset of S-Lang +0.99.38 distribution with some bugfixes and MC-specific code changes. 1.4 Features and Limitations ---------------------------- Internal editor is supported (including syntax highlighting). +Internal viewer is supported (including hex editor). VFS (virtual file system) is not supported. -X11 ports are not supported. +Concurrent subshell is not supported. 2. Changes made --------------- 2.1. Changes to main code ------------------------- -Changes in the main code are enclosed in #ifdef _OS_NT, __os2__ or OS2_NT -blocks. +Changes in the main code are enclosed in #ifdef _OS_NT blocks. -In some cases we suppressed code. This is temporal (so that mc can compile). In -the future we will provide fake or true interfaces for these features. - - Links: creation and information on links are not supported. We +In some cases we suppressed code. This is temporal (so that mc can compile). +In the future we will provide fake or true interfaces for these features. + - Links: creation and information on links are not supported. We should provide a fake interface for the local filesystem and a true one for networked. - GID/UID queries (get_user, owner, preserve UID/GID on copy, ...). - TERMinals: all the code directly done with terminals must be suppressed. - - Signals: deleted. Should support the native ones. + - Signals: deleted. Should support the native ones. - pipes: had some trouble in ext.c and with error_pipes but soon will be fixed. - Chown command: Not supported yet. 2.2. Files rewritten -------------------- -There are several files with so many changes that they have been moved to pc/ -subdirectory. Some of them are common for Win32 and OS/2, some of them are -system-specific. System-specific files bear a clear mark in their names -(for example, dirent_nt.c) -Our intention should be, however, to make most code system-independent. This -would increase code reuse and maintainability :-) +There are several files with so many changes that they have been moved +to pc/ subdirectory. Our intention should be, however, to make most code +system-independent. This would increase code reuse and maintainability. See pc/ subdirectory for further details. 3. Authors and maintainers -------------------------- This port is based on the port for Windows NT by Juan Grigera -and the port for OS/2 by - Alexander Dong -Both ports were merged to one PC port by me, - Pavel Roskin -Please note, that I'm using Linux now. I have access to Windows 95 machines, -but I have no access to OS/2 machines. If you are really keen to continue my -work, please drop me a letter. - -Pavel Roskin +The code is not actively maintained, but the patches are applied. +Please send your changes to the mc-devel list.