newlib-cygwin/winsup/w32api
Corinna Vinschen d81311a800 I forgot 'iprtrmib.h' in the ChangeLog 2000-10-09 09:19:57 +00:00
..
include * include/ntsecapi.h: New file. 2000-10-08 16:55:29 +00:00
lib * include/ntsecapi.h: New file. 2000-10-08 16:55:29 +00:00
ChangeLog I forgot 'iprtrmib.h' in the ChangeLog 2000-10-09 09:19:57 +00:00
Makefile.in import winsup-2000-02-17 snapshot 2000-02-17 19:38:33 +00:00
README import winsup-2000-02-17 snapshot 2000-02-17 19:38:31 +00:00
TODO import winsup-2000-02-17 snapshot 2000-02-17 19:38:33 +00:00
config.guess import winsup-2000-02-17 snapshot 2000-02-17 19:38:33 +00:00
config.sub import winsup-2000-02-17 snapshot 2000-02-17 19:38:33 +00:00
configure import winsup-2000-02-17 snapshot 2000-02-17 19:38:33 +00:00
configure.in import winsup-2000-02-17 snapshot 2000-02-17 19:38:33 +00:00
install-sh import winsup-2000-02-17 snapshot 2000-02-17 19:38:33 +00:00

README

        Free headers and libraries for the Win32 API

        Written by Anders Norlander
        Send bug reports and questions to anorland@hem2.passagen.se
        URL: http://www.acc.umu.se/~anorland/gnu-win32/

* License

  You are free to use, modify and copy this package. No restrictions
  are imposed on programs or object files compiled with this library.
  
  You may not restrict the the usage of this library.

  You may distribute this library as part of another package or as a
  modified package if and only if you do *not* restrict the usage of
  the portions consisting of this (optionally modified) library.

  If distributed as part of another package, please notify the author
  of what you are going to do.  If distributed as a modified package,
  this file *must* be included.

  This library is distributed in the hope that it will be useful, but
  WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

* What is it?

  This is a free set of headers and import libraries for the Win32
  API.  The library differs from the GNU Windows32 library in that I
  have tried to use a file structure that mirrors Microsoft's.  I
  don't like having *all* definitions in one single header as in the
  GNU Windows32 library, I want a clean separation between different
  parts of the API.

  Daniel Guerrero Miralles contributed the DirectX 6.1 import
  libraries and DirectX GUID definitions.

  See the files NOTES and TODO for what needs to be done.

* Size does matter

  Since the WIN32 API is severely bloated (as most MS products seem to
  be) the headers are designed to be as compact as possible, while
  still being readable, in order to minimize parsing time.

  The convention is to omit parameter names for function prototypes,
  no excessive white space. Struct/union members are indented with tab
  characters to make them readable. Comment only when necessary.

  If you are contributing a patch please follow the above mentioned
  convention. Make sure your editor does not convert tabs to spaces.

* What do I need to use it?

  The library is intended for use with egcs 1.1 or later but it is
  possible to use with some other tools as well (although it is not
  very useful). LCC-Win32, MSVC and Borland C++ 5.01 or higher may
  work as well. The import libraries are for GNU tools only.

  The library requires egcs 1.1 or later, since the `#pragma pack'
  feature is used. Mumit Khan provides egcs patches and binaries for
  win32 at `http://www.xraylith.wisc.edu/~khan/software/gnu-win32/'.

  If you are going to use C++ COM objects, you will need a version of
  egcs that recognizes the `comobject' attribute and then define
  HAVE_COMOBJECT when compiling your program. Antonio Mendes de
  Oliveira Neto has a prebuilt version at
  `http://li.facens.br/EGCS-WIN32/english/index.html'. Note that this
  is very experimental. If you want to use COM objects in C++ but with
  C interfaces you must define CINTERFACE.

  Objective-C programs cannot use COM functionality because of
  conflicts between the interface define and the Objective-C
  @interface directive.  There is also a conflict between the windows
  Obj-C BOOL types. To avoid this conflict you should use WINBOOL in
  all places where you would use BOOL in a C/C++ windows program. If
  you include any windows headers *after* `windows.h' you must use the
  method outlined below:

  /* non-windows includes */
  #include <objc/objc.h>
  ...
  /* windows specific headers */
  #include <windows.h>
  #define BOOL WINBOOL
  #include <commctrl.h>
  ...
  #undef BOOL
  ...
  /* include other headers */