-$Id: README.mac,v 1.2 2002/12/13 00:02:48 ben Exp $
+$Id: README.mac,v 1.9 2003/01/05 15:31:45 ben Exp $
Information about PuTTY for the Mac OS
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Install MPW, install the new Universal Headers (optional), then put
the contents of the "68K Static Libraries" directory of the Text
- Encoding Converter SDK into "Interfaces&Libraries:Libraries:Libraries".
+ Encoding Converter SDK into "Interfaces&Libraries:Libraries:Libraries",
+ and the contents of the "Stub Libraries" directory into
+ "Interfaces&Libraries:Libraries:SharedLibraries".
- The "mkputty.mpw" script does most of the work, but currently needs
- you to run "Rez -append -o PuTTY mac_res.r {Includes}" to get the
- resources compiled in. The Makefile currently only generates a
- Classic 68K application. Other architectures will come later.
+ The "mkputty.mpw" script does all the work, and currently producess a
+ Classic 68K build of PuTTY called "PuTTY.68k", a CFM-68K build called
+ "PuTTY.cfm68k", and a non-Carbon PowerPC build called "PuTTY.ppc".
Runtime requirements:
- PuTTY should run on any Macintosh running System 7.0 or later. The
- Classic 68K build seems not to run under Mac OS X (even with
- Classic.app).
+ The Classic 68K build of PuTTY should work on any Macintosh running
+ System 7.0 or later. It runs in the Classic environment in Mac OS X.
+
+ The CFM-68K build of PuTTY should work on any Macintosh with a 68020,
+ 68030 or 68040 processor and with either the CFM-68K Runtime Enabler
+ or Mac OS 7.6.1 or later installed.
+
+ The PowerPC build of PuTTY should work on any Power Macintosh. It
+ runs in the Classic environment in Mac OS X.
Known bugs:
* Display is far too slow.
* Real bold doesn't compensate for changing character widths without Color
QuickDraw. [MAYBE FIXED]
- * sshsha.c and sshmd5.c cause a stack overflow in Apple's PowerPC C compiler
- unless optimisation is entirely disabled.
Features we need (and aren't entirely obvious):
+ * TCP urgent data.
* Scroll-conflation -- scroll_display should change the in-memory
display and remember the scroll, then do_scroll should be called
only when scroll_display gets called for a different rectangle or