| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @tiran for commit 02dc19dd98f2eaa19c2de25eb5a48dec857fa7b1 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
Sorry, something went wrong.
| # like getpath.o with additional -DPY_BOOTSTRAP_PYTHON=1 | ||
| Modules/getpath_bootstrap.o: $(srcdir)/Modules/getpath.c Python/frozen_modules/getpath.h Makefile $(PYTHON_HEADERS) | ||
| $(CC) -c $(PY_CORE_CFLAGS) -DPYTHONPATH='"$(PYTHONPATH)"' \ | ||
| -DPREFIX='"$(prefix)"' \ | ||
| -DEXEC_PREFIX='"$(exec_prefix)"' \ | ||
| -DVERSION='"$(VERSION)"' \ | ||
| -DVPATH='"$(VPATH)"' \ | ||
| -DPLATLIBDIR='"$(PLATLIBDIR)"' \ | ||
| -DPY_BOOTSTRAP_PYTHON=1 \ | ||
| -o $@ $(srcdir)/Modules/getpath.c |
There was a problem hiding this comment.
Wouldn't it be more elegant to have a two-line file named getpath_bootstrap.c using the default .c.o rule?
#define BOOTSTRAP_PYTHON 1
#include "getpath.c"
Sorry, something went wrong.
There was a problem hiding this comment.
I agree that the approach is not elegant. getpath.c requires additional macros
Lines 24 to 28 in ddbab69
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
…g framework
https://bugs.python.org/issue45950