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>
62 lines
2.1 KiB
C
62 lines
2.1 KiB
C
|
|
/* Tuple object interface */
|
|
|
|
#ifndef Py_TUPLEOBJECT_H
|
|
#define Py_TUPLEOBJECT_H
|
|
#ifdef __cplusplus
|
|
extern "C" {
|
|
#endif
|
|
|
|
/*
|
|
Another generally useful object type is a tuple of object pointers.
|
|
For Python, this is an immutable type. C code can change the tuple items
|
|
(but not their number), and even use tuples are general-purpose arrays of
|
|
object references, but in general only brand new tuples should be mutated,
|
|
not ones that might already have been exposed to Python code.
|
|
|
|
*** WARNING *** PyTuple_SetItem does not increment the new item's reference
|
|
count, but does decrement the reference count of the item it replaces,
|
|
if not nil. It does *decrement* the reference count if it is *not*
|
|
inserted in the tuple. Similarly, PyTuple_GetItem does not increment the
|
|
returned item's reference count.
|
|
*/
|
|
|
|
typedef struct {
|
|
PyObject_VAR_HEAD
|
|
PyObject *ob_item[1];
|
|
|
|
/* ob_item contains space for 'ob_size' elements.
|
|
* Items must normally not be NULL, except during construction when
|
|
* the tuple is not yet visible outside the function that builds it.
|
|
*/
|
|
} PyTupleObject;
|
|
|
|
PyAPI_DATA(PyTypeObject) PyTuple_Type;
|
|
|
|
#define PyTuple_Check(op) \
|
|
PyType_FastSubclass(Py_TYPE(op), Py_TPFLAGS_TUPLE_SUBCLASS)
|
|
#define PyTuple_CheckExact(op) (Py_TYPE(op) == &PyTuple_Type)
|
|
|
|
PyAPI_FUNC(PyObject *) PyTuple_New(Py_ssize_t size);
|
|
PyAPI_FUNC(Py_ssize_t) PyTuple_Size(PyObject *);
|
|
PyAPI_FUNC(PyObject *) PyTuple_GetItem(PyObject *, Py_ssize_t);
|
|
PyAPI_FUNC(int) PyTuple_SetItem(PyObject *, Py_ssize_t, PyObject *);
|
|
PyAPI_FUNC(PyObject *) PyTuple_GetSlice(PyObject *, Py_ssize_t, Py_ssize_t);
|
|
PyAPI_FUNC(int) _PyTuple_Resize(PyObject **, Py_ssize_t);
|
|
PyAPI_FUNC(PyObject *) PyTuple_Pack(Py_ssize_t, ...);
|
|
PyAPI_FUNC(void) _PyTuple_MaybeUntrack(PyObject *);
|
|
|
|
/* Macro, trading safety for speed */
|
|
#define PyTuple_GET_ITEM(op, i) (((PyTupleObject *)(op))->ob_item[i])
|
|
#define PyTuple_GET_SIZE(op) Py_SIZE(op)
|
|
|
|
/* Macro, *only* to be used to fill in brand new tuples */
|
|
#define PyTuple_SET_ITEM(op, i, v) (((PyTupleObject *)(op))->ob_item[i] = v)
|
|
|
|
PyAPI_FUNC(int) PyTuple_ClearFreeList(void);
|
|
|
|
#ifdef __cplusplus
|
|
}
|
|
#endif
|
|
#endif /* !Py_TUPLEOBJECT_H */
|