Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
061ac50e
Commit
061ac50e
authored
Oct 22, 1996
by
Jack Jansen
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added a note about PythonApplet name
parent
baffd68a
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
12 deletions
+11
-12
Mac/Demo/building.html
Mac/Demo/building.html
+11
-12
No files found.
Mac/Demo/building.html
View file @
061ac50e
...
@@ -48,7 +48,7 @@ Think/Symantec C but you are basically on your own.
...
@@ -48,7 +48,7 @@ Think/Symantec C but you are basically on your own.
<LI>
You need GUSI, the Grand Unified Socket Interface, by Matthias
<LI>
You need GUSI, the Grand Unified Socket Interface, by Matthias
Neeracher. The current distribution has been built with a modified version of
Neeracher. The current distribution has been built with a modified version of
CWGUSI 1.
7.2
. CWGUSI is
CWGUSI 1.
8.0
. CWGUSI is
obtainable from
<A
obtainable from
<A
HREF=
"ftp://ftp.switch.ch/software/mac/src/mw_c"
>
ftp://ftp.switch.ch/software/mac/src/mw_c
</A>
.
HREF=
"ftp://ftp.switch.ch/software/mac/src/mw_c"
>
ftp://ftp.switch.ch/software/mac/src/mw_c
</A>
.
It is possible to build a non-GUSI Python, see below.
It is possible to build a non-GUSI Python, see below.
...
@@ -374,7 +374,7 @@ can change the gusi settings should you feel like doing so). Do
...
@@ -374,7 +374,7 @@ can change the gusi settings should you feel like doing so). Do
<em>
not
</em>
run it yet, this will possibly result in a garbled
<em>
not
</em>
run it yet, this will possibly result in a garbled
preferences file.
<p>
preferences file.
<p>
<DT>
PythonApplet
<DT>
PythonApplet
PPC
<DD>
The applet skeleton application. Very similar to
<DD>
The applet skeleton application. Very similar to
<code>
PythonPPC
</code>
, but it calls to a different entrypoint in the
<code>
PythonPPC
</code>
, but it calls to a different entrypoint in the
core library. The
<code>
mkapplet
</code>
script will copy this complete
core library. The
<code>
mkapplet
</code>
script will copy this complete
...
@@ -383,16 +383,15 @@ applet. <p>
...
@@ -383,16 +383,15 @@ applet. <p>
</DL>
</DL>
After creating the alias to
<code>
PythonCore
</code>
you should move
After creating the alias to
<code>
PythonCorePPC
</code>
you should move
<code>
PythonPPC
</code>
to the main Python folder. Next you remove any
<code>
PythonPPC
</code>
to the main Python folder. Next you remove any old
old
<code>
Python Preferences
</code>
file from the
<code>
Python XXX Preferences
</code>
file from the
<code>
Preferences
</code>
folder
<code>
Preferences
</code>
folder (if you had python installed on your
(if you had python installed on your system before) and run the interpreter once
system before) and run the interpreter once to create the correct
to create the correct preferences file. You should also make an alias
preferences file. You should also make an alias to
<code>
PythonApplet
</code>
pointing to
<code>
PythonAppletPPC
</code>
in the main
<code>
PythonApplet
</code>
in the main Python folder. (again: making an
Python folder. (again: making an alias is preferrable to copying or moving the
alias is preferrable to copying or moving the file, since this will
file, since this will cause the correct file to be used if you ever rebuild
cause the correct file to be used if you ever rebuild
PythonAppletPPC).
<p>
PythonApplet).
<p>
Next, you have to build the extension modules in the
Next, you have to build the extension modules in the
<code>
PlugIns
</code>
folder. Open each project with
<code>
.ppc
</code>
in the
<code>
PlugIns
</code>
folder. Open each project with
<code>
.ppc
</code>
in the
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment