traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Restructured MPW notes

This commit is contained in:
Guido van Rossum 1994-08-29 09:14:14 +00:00
parent 8ce65b4cde
commit 8e1f8dd094
2 changed files with 46 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
Mac/README
View File

@ -143,17 +143,29 @@ copies resources into the application file from a file
================
The subdirectory MPW contains a README.MPW file, a buildall script and
several Makefiles (in respective subdirectories), kindly contributed
by Richard Walker of Island Software. Move these files to the
corresponding locations relative to the Python root directory, and run
the buildall script. The README.MPW file contains more instructions
and caveats (I've added some remarks of my own at the end). I haven't
tried building STDWIN with MPW recently (there is MPW specific code
all over the STDWIN source but it is for a much older version of the
compiler and library). The MPW and THINK C ports share all source
files, including config.c and config.h -- all differentiation is done
based on #ifdef THINK_C or #ifdef MPW (#ifdef macintosh is used for
code that should be seen by all Mac compilers).
several Makefiles, kindly contributed by Richard Walker of Island
Software. Move these files to the corresponding locations relative to
the Python root directory (where Mac-Makefile should become Makefile
in the Mac subdirectory, etc.), and run the buildall script. The
README.MPW file contains more instructions and caveats (I've added
some remarks of my own at the end).
Some notes:
- The MPW and THINK C ports share all source files, including config.c
and config.h -- all differentiation is done based on #ifdef THINK_C
or #ifdef MPW (#ifdef macintosh is used for code that should be seen
by all Mac compilers).
- The dynload subdirectory contains an attempt to create dynamically
loadable modules from CODE segments. This was not very successful
due to the restrictions on CODE segments (no global variables, no
calls to external functions). Maybe Apple's new shared library
manager will be a better starting point.
- I haven't tried building STDWIN with MPW recently. There is MPW
specific code all over the STDWIN source but it is for a much older
version of the compiler and library.
--Guido van Rossum, CWI, Amsterdam <Guido.van.Rossum@cwi.nl>

34
Mac/Relnotes-1.2
View File

@ -143,17 +143,29 @@ copies resources into the application file from a file
================
The subdirectory MPW contains a README.MPW file, a buildall script and
several Makefiles (in respective subdirectories), kindly contributed
by Richard Walker of Island Software. Move these files to the
corresponding locations relative to the Python root directory, and run
the buildall script. The README.MPW file contains more instructions
and caveats (I've added some remarks of my own at the end). I haven't
tried building STDWIN with MPW recently (there is MPW specific code
all over the STDWIN source but it is for a much older version of the
compiler and library). The MPW and THINK C ports share all source
files, including config.c and config.h -- all differentiation is done
based on #ifdef THINK_C or #ifdef MPW (#ifdef macintosh is used for
code that should be seen by all Mac compilers).
several Makefiles, kindly contributed by Richard Walker of Island
Software. Move these files to the corresponding locations relative to
the Python root directory (where Mac-Makefile should become Makefile
in the Mac subdirectory, etc.), and run the buildall script. The
README.MPW file contains more instructions and caveats (I've added
some remarks of my own at the end).
Some notes:
- The MPW and THINK C ports share all source files, including config.c
and config.h -- all differentiation is done based on #ifdef THINK_C
or #ifdef MPW (#ifdef macintosh is used for code that should be seen
by all Mac compilers).
- The dynload subdirectory contains an attempt to create dynamically
loadable modules from CODE segments. This was not very successful
due to the restrictions on CODE segments (no global variables, no
calls to external functions). Maybe Apple's new shared library
manager will be a better starting point.
- I haven't tried building STDWIN with MPW recently. There is MPW
specific code all over the STDWIN source but it is for a much older
version of the compiler and library.
--Guido van Rossum, CWI, Amsterdam <Guido.van.Rossum@cwi.nl>