mirror of
https://github.com/python/cpython.git
synced 2025-08-17 07:11:51 +00:00
f18d5cea53
svn+ssh://pythondev@svn.python.org/python/trunk ........ r73286 | georg.brandl | 2009-06-08 09:57:35 +0200 (Mo, 08 Jun 2009) | 1 line Remove period from end of headings. ........ r73294 | georg.brandl | 2009-06-08 15:34:52 +0200 (Mo, 08 Jun 2009) | 1 line #6194: O_SHLOCK/O_EXLOCK are not really more platform independent than lockf(). ........ r73296 | georg.brandl | 2009-06-08 18:03:41 +0200 (Mo, 08 Jun 2009) | 1 line #6238: add fillchar to string.just function family. ........ r73459 | raymond.hettinger | 2009-06-17 03:43:47 +0200 (Mi, 17 Jun 2009) | 1 line Add usage note. ........ r73462 | georg.brandl | 2009-06-17 11:36:21 +0200 (Mi, 17 Jun 2009) | 1 line #6295: clarify blocking behavior of getch(). ........ r73463 | georg.brandl | 2009-06-17 11:43:31 +0200 (Mi, 17 Jun 2009) | 1 line #6255: document PyInt_FromSize_t. ........ r73544 | georg.brandl | 2009-06-24 08:41:19 +0200 (Mi, 24 Jun 2009) | 1 line #6332: fix word dupes throughout the source. ........ r73576 | benjamin.peterson | 2009-06-27 01:37:06 +0200 (Sa, 27 Jun 2009) | 1 line document is_declared_global() ........ r73577 | benjamin.peterson | 2009-06-27 16:16:23 +0200 (Sa, 27 Jun 2009) | 1 line link to extensive generator docs in the reference manual ........ r73595 | ezio.melotti | 2009-06-28 01:45:39 +0200 (So, 28 Jun 2009) | 1 line stmt and setup can contain multiple statements, see #5896 ........ r73596 | ezio.melotti | 2009-06-28 02:07:45 +0200 (So, 28 Jun 2009) | 1 line Fixed a wrong apostrophe ........ r73693 | jesse.noller | 2009-06-29 20:20:34 +0200 (Mo, 29 Jun 2009) | 1 line Bug 5906: add a documentation note for unix daemons vs. multiprocessing daemons ........ r73694 | jesse.noller | 2009-06-29 20:24:26 +0200 (Mo, 29 Jun 2009) | 1 line Issue 5740: multiprocessing.connection.* authkey fixes ........ r73704 | georg.brandl | 2009-06-30 18:15:43 +0200 (Di, 30 Jun 2009) | 1 line #6376: fix copy-n-paste oversight. ........ r73705 | georg.brandl | 2009-06-30 18:17:28 +0200 (Di, 30 Jun 2009) | 1 line #6374: add a bit of explanation about shell=True on Windows. ........ r73707 | georg.brandl | 2009-06-30 18:35:11 +0200 (Di, 30 Jun 2009) | 1 line #6371: fix link targets. ........ r73713 | ezio.melotti | 2009-07-01 00:56:16 +0200 (Mi, 01 Jul 2009) | 1 line Fixed a backslash that was not supposed to be there ........ r73937 | georg.brandl | 2009-07-11 12:12:36 +0200 (Sa, 11 Jul 2009) | 1 line Fix style. ........ r73938 | georg.brandl | 2009-07-11 12:14:54 +0200 (Sa, 11 Jul 2009) | 1 line #6446: fix import_spam() function to use correct error and reference handling. ........ r73939 | georg.brandl | 2009-07-11 12:18:10 +0200 (Sa, 11 Jul 2009) | 1 line #6448: clarify docs for find_module(). ........ r73940 | georg.brandl | 2009-07-11 12:37:38 +0200 (Sa, 11 Jul 2009) | 1 line #6430: add note about size of "u" type. ........ r73945 | georg.brandl | 2009-07-11 12:51:31 +0200 (Sa, 11 Jul 2009) | 1 line #6456: clarify the meaning of constants used as arguments to nl_langinfo(). ........ r73951 | georg.brandl | 2009-07-11 16:23:38 +0200 (Sa, 11 Jul 2009) | 2 lines array.array is actually a class. ........ r73979 | benjamin.peterson | 2009-07-12 18:56:54 +0200 (So, 12 Jul 2009) | 1 line add versionadded ........
42 lines
1.9 KiB
Text
42 lines
1.9 KiB
Text
Q. I want to port Python to a new platform. How do I begin?
|
|
|
|
A. I guess the two things to start with is to familiarize yourself
|
|
with are the development system for your target platform and the
|
|
generic build process for Python. Make sure you can compile and run a
|
|
simple hello-world program on your target platform. Make sure you can
|
|
compile and run the Python interpreter on a platform to which it has
|
|
already been ported (preferably Unix, but Mac or Windows will do,
|
|
too).
|
|
|
|
I also would never start something like this without at least
|
|
medium-level understanding of your target platform (i.e. how it is
|
|
generally used, how to write platform specific apps etc.) and Python
|
|
(or else you'll never know how to test the results).
|
|
|
|
The build process for Python, in particular the Makefiles in the
|
|
source distribution, will give you a hint on which files to compile
|
|
for Python. Not all source files are relevant -- some are platform
|
|
specific, others are only used in emergencies (e.g. getopt.c). The
|
|
Makefiles tell the story.
|
|
|
|
You'll also need a pyconfig.h file tailored for your platform. You can
|
|
start with pyconfig.h.in, read the comments and turn on definitions that
|
|
apply to your platform.
|
|
|
|
And you'll need a config.c file, which lists the built-in modules you
|
|
support. Start with Modules/config.c.in.
|
|
|
|
Finally, you'll run into some things that aren't supported on your
|
|
target platform. Forget about the posix module for now -- simply take
|
|
it out of the config.c file.
|
|
|
|
Bang on it until you get a >>> prompt. (You may have to disable the
|
|
importing of "site.py" and "exceptions.py" by passing -X and -S
|
|
options.
|
|
|
|
Then bang on it until it executes very simple Python statements.
|
|
|
|
Now bang on it some more. At some point you'll want to use the os
|
|
module; this is the time to start thinking about what to do with the
|
|
posix module. It's okay to simply #ifdef out those functions that
|
|
cause problems; the remaining ones will be quite useful.
|