summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorMichael R Sweet <michael.r.sweet@gmail.com>1998-12-02 17:25:40 +0000
committerMichael R Sweet <michael.r.sweet@gmail.com>1998-12-02 17:25:40 +0000
commit5fe9ef7d19f1c928ee31062686e0b4d6fa194921 (patch)
tree3a37bffc30dfa7d72451aa78771584dbaa80172a /README
parent4d1fe8dd6fbcc7eb07f62ab70cfbee5a2c273834 (diff)
Updated to always call WIN32 or Windows "Microsoft Windows".
git-svn-id: file:///fltk/svn/fltk/trunk@118 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'README')
-rw-r--r--README13
1 files changed, 7 insertions, 6 deletions
diff --git a/README b/README
index 238622328..7391c1463 100644
--- a/README
+++ b/README
@@ -4,8 +4,8 @@ README - Fast Light Tool Kit (FLTK) Version 1.0
WHAT IS FLTK?
FLTK (pronounced "fulltick") is a LGPL'd C++ graphical user
- interface toolkit for X (UNIX(r)), OpenGL, and WIN32 (Microsoft(r)
- Windows(r) NT 4.0, 95, or 98). It is currently maintained by a small
+ interface toolkit for X (UNIX(r)), OpenGL, and Microsoft(r)
+ Windows(r) NT 4.0, 95, or 98. It is currently maintained by a small
group of developers across the world with a central repository in
the US.
@@ -158,6 +158,7 @@ BUILDING FLTK UNDER OS/2
To build the XFree86 version of FLTK for OS/2, copy the appropriate
makeinclude and config files to the main directory and do a make:
+ cp makefiles/Makefile.os2x Makefile
cp makefiles/makeinclude.os2x makeinclude
cp makefiles/config.os2x config.h
make
@@ -233,10 +234,10 @@ HOW TO WRITE PROGRAMS THAT USE FLTK
switches. If not you will need to provide a "-Idir" switch
pointing to this directory (all the headers are in ./FL).
- Windows developers please note: case *is* significant under other
- operating systems, and the C standard uses the forward slash (/) to
- separate directories. The following #include directives are *not*
- recommended for portability reasons:
+ Microsoft Windows developers please note: case *is* significant
+ under other operating systems, and the C standard uses the forward
+ slash (/) to separate directories. The following #include
+ directives are *not* recommended for portability reasons:
#include <fl\fl_xyz.h>
#include <fl/fl_xyz.h>