Mercurial > emacs
comparison nt/INSTALL @ 93668:2368e43fd306
Update W32 API requirements.
author | Jason Rumney <jasonr@gnu.org> |
---|---|
date | Fri, 04 Apr 2008 22:05:45 +0000 |
parents | f991f10f15ec |
children | 0573bdbac2e6 |
comparison
equal
deleted
inserted
replaced
93667:f8942531c106 | 93668:2368e43fd306 |
---|---|
363 | 363 |
364 When configure runs, it attempts to detect when GCC itself, or the | 364 When configure runs, it attempts to detect when GCC itself, or the |
365 headers it is using, are not suitable for building Emacs. GCC version | 365 headers it is using, are not suitable for building Emacs. GCC version |
366 2.95 or later is needed, because that is when the Windows port gained | 366 2.95 or later is needed, because that is when the Windows port gained |
367 sufficient support for anonymous structs and unions to cope with some | 367 sufficient support for anonymous structs and unions to cope with some |
368 definitions from winnt.h that are used by addsection.c. The W32 API | 368 definitions from winnt.h that are used by addsection.c. |
369 headers that come with Cygwin b20.1 are incomplete, and do not include | 369 Older versions of the W32 API headers that come with Cygwin and MinGW |
370 some definitions required by addsection.c, for instance. Also, older | 370 may be missing some definitions required by Emacs, or broken in other |
371 releases of the W32 API headers from Anders Norlander contain a typo | 371 ways. In particular, uniscribe APIs were added to mingw cvs on |
372 in the definition of IMAGE_FIRST_SECTION in winnt.h, which | 372 2006-03-26, so releases from before then cannot be used. |
373 addsection.c relies on. Versions of w32api-xxx.zip from at least | |
374 1999-11-18 onwards are okay. | |
375 | 373 |
376 When in doubt about correctness of what configure did, look at the file | 374 When in doubt about correctness of what configure did, look at the file |
377 config.log, which shows all the failed test programs and compiler | 375 config.log, which shows all the failed test programs and compiler |
378 messages associated with the failures. If that doesn't give a clue, | 376 messages associated with the failures. If that doesn't give a clue, |
379 please report the problems, together with the relevant fragments from | 377 please report the problems, together with the relevant fragments from |