shenleiandClaude Opus 5
5fad769ee8
The embedded 40250 script layer needs its own interpreter on five platforms. 2.7 is end-of-life, so nothing can be fetched from the target SDKs and the source is vendored (official 2.7.18 tarball, trimmed to 25MB; Lib/ stays for step 3's python27.zip). cpython-2.7.18/CMakeLists.txt builds one `mtpython` static library from exactly the 133 objects the reference libpython2.7.a contains, off by default behind -DMTGODOT_EMBED_PYTHON=ON. The source list and the built-in module table (config/config.c, 39 entries) are shared; pyconfig.h is a probe result and is not, so each platform keeps its own under config/<platform>/, regenerated by tools/py_embed/gen_pyconfig.sh and checked against the shared table. Three vendor patches, documented in docs/THIRD-PARTY.md: configure/configure.ac learn arm64 on macOS, and posixmodule.c undefines the process-control calls it hard-defines past pyconfig.h when building for iOS. macOS (ctest python.embed: every builtin imports, codecs and pickle work off the vendored Lib/), Android arm64 and iOS arm64 build. Linux needs a Linux host and Windows needs a MinGW-vs-MSVC decision; both are noted for step 4. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
29 lines
646 B
C
29 lines
646 B
C
|
|
/* Range object interface */
|
|
|
|
#ifndef Py_RANGEOBJECT_H
|
|
#define Py_RANGEOBJECT_H
|
|
#ifdef __cplusplus
|
|
extern "C" {
|
|
#endif
|
|
|
|
/* This is about the type 'xrange', not the built-in function range(), which
|
|
returns regular lists. */
|
|
|
|
/*
|
|
A range object represents an integer range. This is an immutable object;
|
|
a range cannot change its value after creation.
|
|
|
|
Range objects behave like the corresponding tuple objects except that
|
|
they are represented by a start, stop, and step datamembers.
|
|
*/
|
|
|
|
PyAPI_DATA(PyTypeObject) PyRange_Type;
|
|
|
|
#define PyRange_Check(op) (Py_TYPE(op) == &PyRange_Type)
|
|
|
|
#ifdef __cplusplus
|
|
}
|
|
#endif
|
|
#endif /* !Py_RANGEOBJECT_H */
|