From 4020a21f975bed0d36b32805c4e300523b7a5575 Mon Sep 17 00:00:00 2001 From: "Dimitrie O. Paun" Date: Thu, 2 Oct 2003 04:25:44 +0000 Subject: [PATCH] Add author list as with the other guides. Small cleanups. --- documentation/winelib-bindlls.sgml | 16 ++++++++-------- documentation/winelib-mfc.sgml | 7 ------- documentation/winelib-porting.sgml | 22 +++------------------- documentation/winelib-user.sgml | 16 ++++++++++++++++ 4 files changed, 27 insertions(+), 34 deletions(-) diff --git a/documentation/winelib-bindlls.sgml b/documentation/winelib-bindlls.sgml index e121a473d7d..faad7a86f7f 100644 --- a/documentation/winelib-bindlls.sgml +++ b/documentation/winelib-bindlls.sgml @@ -1,9 +1,10 @@ - Using Linux libraries as DLLs + + Building WineLib DLLs Introduction - For one reason or another you may find yourself with a Linux shared + For one reason or another you may find yourself with a Linux library that you want to use as if it were a Windows Dll. There are various reasons for this including the following: @@ -17,14 +18,14 @@ There is a well-defined interface available and there are several - Linux solutions that are available for it. - (The ODBC interface in Wine) + Linux solutions that are available for it + (e.g. the ODBC interface in Wine). - You wish to do something that you can do in Linux but Wine does - not yet support it. + You have a binary only Windows application that can be extended + through plugins, such as a text editor or IDE. @@ -184,8 +185,7 @@ signed short WINAPI MyProxyWinFunc (unsigned short a, void *b, void *c, is quite long it is extremely simple in structure. - The MAIN_OdbcInit function is the function that was named in the - spec file as the init function. + DllMain the function is used to initialize the DLL. On the process attach event the function dynamically links to the desired Linux ODBC library (since there are several available) and builds a list of function pointers. It unlinks on the process diff --git a/documentation/winelib-mfc.sgml b/documentation/winelib-mfc.sgml index 3d07071466c..d71d254d022 100644 --- a/documentation/winelib-mfc.sgml +++ b/documentation/winelib-mfc.sgml @@ -46,19 +46,12 @@ Legal issues - - (Extracted from the HOWTO-Winelib written by Wilbur Dale - <wilbur.dale@lumin.nl>) - The purpose of this section is to make you aware of potential legal problems. Be sure to read your licenses and to consult your lawyers. In any case you should not consider the remainder of this section to be authoritative since it has not been written by a lawyer. - - Well, let's try to have a look at the situation anyway. - During the compilation of your program, you will be combining code from several sources: your code, Winelib code, Microsoft MFC code, diff --git a/documentation/winelib-porting.sgml b/documentation/winelib-porting.sgml index 71f6f2f672a..65a6cdafa64 100644 --- a/documentation/winelib-porting.sgml +++ b/documentation/winelib-porting.sgml @@ -6,12 +6,11 @@ The wchar_t type has different standard - sizes in Unix (4 bytes) and Windows (2 bytes). Recent versions - of gcc (2.9.7 or later) support the + sizes in Unix (4 bytes) and Windows (2 bytes). You need a + recent gcc version (2.9.7 or later) that supports the -fshort-wchar option to set the size of wchar_t to the one expected - by Windows applications. Pass this option to every file - that is built. + by Windows applications. @@ -21,26 +20,11 @@ the msvcrt runtime library instead of glibc. The functions in glibc will not work correctly with 16 bit strings. - - To prevent warnings when declaring a single unicode character - in C, use (WCHAR)L'x', rather than - __TEXT('x'). This works on Windows also. - C library - - There are 2 choices available to you regarding which C library to use: the native glibc C library or the msvcrt C library. diff --git a/documentation/winelib-user.sgml b/documentation/winelib-user.sgml index cc3cbc37ede..f1ce9e68eee 100644 --- a/documentation/winelib-user.sgml +++ b/documentation/winelib-user.sgml @@ -12,6 +12,22 @@ Winelib User's Guide + + &intro;