From 8f692f271d4716464efaea2d4f9800ac4711a0d8 Mon Sep 17 00:00:00 2001 From: "Dimitrie O. Paun" Date: Mon, 15 Sep 2003 20:08:47 +0000 Subject: [PATCH] Update the porting documentation. --- documentation/porting.sgml | 244 ++----------------------------------- 1 file changed, 8 insertions(+), 236 deletions(-) diff --git a/documentation/porting.sgml b/documentation/porting.sgml index 0c21b5c8e8c..9cafcb8fffb 100644 --- a/documentation/porting.sgml +++ b/documentation/porting.sgml @@ -6,44 +6,9 @@ Porting - written by ??? + This document provides a few tips on porting Wine to your + favorite operating system. - - (Extracted from wine/documentation/how-to-port) - - - - What is this? - - - This note is a short description of: - - - - - - How to port Wine to your favorite operating system - - - - - Why you probably shouldn't use #ifdef MyOS - - - - - What to do instead. - - - - - - This document does not say a thing about how to port Wine to - non-386 operating systems, though. You would need a CPU - emulator. Let's get Wine into a better shape on 386 first, - OK? - - Why <symbol>#ifdef MyOS</symbol> is probably a mistake. @@ -90,16 +55,11 @@ bugs in header files, library functions, the compiler, ... - - - (you name it) - - You will need Gnu Autoconf, which you can get from your friendly Gnu mirror. This program takes Wine's - configure.in file and produces a + configure.ac file and produces a configure shell script that users use to configure Wine to their system. @@ -107,7 +67,11 @@ There are exceptions to the "avoid #ifdef MyOS" rule. Wine, for example, needs the internals of the signal stack -- that cannot easily be - described in terms of features. + described in terms of features. Moreover, you can not use + autoconf's HAVE_* + symbols in Wine's headers, as these may be used by Winelib + users who may not be using a configure + script. Let's now turn to specific porting problems and how to solve @@ -248,198 +212,6 @@ AC_CHECK_HEADER(foo.h, AC_DEFINE(HAVE_FOO_H)) - - Running & Compiling Wine in OS/2 - - - Written by &name-robert-pouliot; &email-robert-pouliot;, - January 9, 1997 - - - (Extracted from wine/documentation/wine_os2) - - - - If you want to help the port of Wine to OS/2, send me a - message at krynos@clic.net I currently don't - want beta testers. It must work before we can test it. - - - Here is what you need to (try to) compile Wine for OS/2: - - - - - - EMX 0.9c (fix 2) - - - - - XFree86 3.2 OS/2 (with development libraries) - - - - - bash, gnu make, - grep, tar, - bison, flex - - - - - sed (a working copy of) - - - - - diff and patch - are recommended - - - - - Lots of disk space (about 40-50 megs after EMX and XFree installed) - - - - - - To compile: - - - -$ sh -$ tools/make_os2.sh -$ make depend -$ make -$ emxbind wine - - - - Currently: - - - - - - configure and make depend work... - - - - - make compiles (with a modified - Linux mman.h), but doesn't - link. - - - - - signal handling is horrible... (if any) - - - - - EMX doesn't support mmap (and - related), SysV IPC and stafs() - - - - - XFree86/OS2 3.2 doesn't support - XShmQueryExtension() and - XShmPixmapFormat() due to the same - lack in EMX... - - - - - - What needs to be redone: - - - - - - LDT (using DosAllocSeg in - memory/ldt.c) * - - - - - Implement mmap() and SysV IPC in EMX * - - - - - File functions, - - - - - I/O access (do it!), - - - - - Communication (modem), - - - - - Interrupt (if int unknown, call current RealMode one...), - - - - - Verify that everything is thread safe (how does Win95/NT handle multi-thread?), - - - - - Move X functions in some files (and make a wrapper, to use PM instead latter), - - - - - Return right CPU type, - - - - - Make winsock work - - - - - - The good things: - - - - - - OS/2 have DOS interrupts - - - - - OS/2 have I/O port access - - - - - OS/2 have multi-thread - - - - - Merlin have Open32 (to be used later...) - - - - -