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>
24 lines
623 B
C
24 lines
623 B
C
#include "pyconfig.h"
|
|
#include "pyfpe.h"
|
|
/*
|
|
* The signal handler for SIGFPE is actually declared in an external
|
|
* module fpectl, or as preferred by the user. These variable
|
|
* definitions are required in order to compile Python without
|
|
* getting missing externals, but to actually handle SIGFPE requires
|
|
* defining a handler and enabling generation of SIGFPE.
|
|
*/
|
|
|
|
#ifdef WANT_SIGFPE_HANDLER
|
|
jmp_buf PyFPE_jbuf;
|
|
int PyFPE_counter = 0;
|
|
#endif
|
|
|
|
/* Have this outside the above #ifdef, since some picky ANSI compilers issue a
|
|
warning when compiling an empty file. */
|
|
|
|
double
|
|
PyFPE_dummy(void *dummy)
|
|
{
|
|
return 1.0;
|
|
}
|