[issue16235] Add python-config.sh for use during cross compilation.

Change by Éric Araujo : -- Removed message: https://bugs.python.org/msg405026 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue16235] Add python-config.sh for use during cross compilation.

surbhi nahta added the comment: Hi, I am also having the same issue and found the best answer on the below site - https://python-9.jimdosite.com/ -- nosy: +nahtasurbhi123 ___ Python tracker ___

[issue16235] Add python-config.sh for use during cross compilation.

Ray Donnelly added the comment: Thank you Matthias! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue16235] Add python-config.sh for use during cross compilation.

Matthias Klose added the comment: now committed, using stdin for sed. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue16235] Add python-config.sh for use during cross compilation.

Roundup Robot added the comment: New changeset c0370730b364 by doko in branch 'default': - Issue #16235: Implement python-config as a shell script. http://hg.python.org/cpython/rev/c0370730b364 -- nosy: +python-dev ___ Python tracker

[issue16235] Add python-config.sh for use during cross compilation.

Ray Donnelly added the comment: Great. My only query is whether the changes to sed will work on non-GNU sed. It used to be like: sed < in >out you've now got: sed in >out I'm not saying it won't work, I'm not in a position to check, but I think it's safer to keep it as it was. -- __

[issue16235] Add python-config.sh for use during cross compilation.

Matthias Klose added the comment: so here is what I intend to commit. - --help now does exit with 0 (same as the python script) - removed the abi safety check (always compares the same two strings) - build the script for the build target, so that it can be checked before installing it.

[issue16235] Add python-config.sh for use during cross compilation.

Ray Donnelly added the comment: New patch attached: LIBPL changed to a more direct AC_SUBST and PLATINCDIR used for --includes and --cflags. -- Added file: http://bugs.python.org/file28164/-add-python-config-sh.patch ___ Python tracker

[issue16235] Add python-config.sh for use during cross compilation.

Matthias Klose added the comment: oh, the equivalent for flags = ['-I' + sysconfig.get_path('include'), '-I' + sysconfig.get_path('platinclude')] is still missing. I know that both scripts versions are only run post-install, but let's have the same output. background:

[issue16235] Add python-config.sh for use during cross compilation.

Matthias Klose added the comment: looks fine, just one more minor issue: please use @LIBPL@ directly. there's no feedback from others, so I think this should go in as the extra script first, and not replace the original one immediately. -- ___ Pytho

[issue16235] Add python-config.sh for use during cross compilation.

Ray Donnelly added the comment: I've addressed everything (local, ABIFLAGS) except the platform includes. AFAICT, platform includes only differs from includes during the Python build phase. This script can only be run post-install. I also added --extension-suffix, tidied it up and allowed it t

[issue16235] Add python-config.sh for use during cross compilation.

Ray Donnelly added the comment: > hmm, but python.pc, _sysconfigdata.py and Makefile still have this > information. In my experience, as long as PYTHONHOME is set correctly before the Python .so, .dll or .dylib is loaded then everything works correctly. >From what I've seen, .pc files are als

[issue16235] Add python-config.sh for use during cross compilation.

Matthias Klose added the comment: Am 07.11.2012 13:52, schrieb Ray Donnelly: > > Ray Donnelly added the comment: > >> is there a need for the built vs. installed prefix? >> this is logic not found in the python implementation. >> what is this supposed to do? > > You are right, it is not f

[issue16235] Add python-config.sh for use during cross compilation.

Ray Donnelly added the comment: > is there a need for the built vs. installed prefix? >this is logic not found in the python implementation. >what is this supposed to do? You are right, it is not found in the original python implementation, but I feel that it's useful. Without it, you c

[issue16235] Add python-config.sh for use during cross compilation.

Changes by Matthias Klose : -- nosy: +georg.brandl, loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue16235] Add python-config.sh for use during cross compilation.

Matthias Klose added the comment: see issue #1161914 for the original script. > 2) Since we are Pythoneers, why write this script as a > shell-script instead of a Python script? (sh may not even be > available on Windows). python-config is usally not used by python module builds, but third part

[issue16235] Add python-config.sh for use during cross compilation.

Ray Donnelly added the comment: I also checked the Windows releases and python-config isn't included. However, I don't think there's a good reason for that. python-config would in theory work fine if people wanted to link their programs to Python on Windows, as would python-config.sh given a p

[issue16235] Add python-config.sh for use during cross compilation.

Ray Donnelly added the comment: I agree in principle about not having to maintain two implementations but I would worry about breaking external packages that depend on the python implementation. In the meantime, please find an updated version of this patch that adds support for --configdir -

[issue16235] Add python-config.sh for use during cross compilation.

Matthias Klose added the comment: Earlier, we had the shell script, now we have the python implementation, which doesn't work for cross builds. On the other hand, I don't like to have two implementations which need to be kept in sync. So my proposal would be to discard the python implementatio

[issue16235] Add python-config.sh for use during cross compilation.

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue16235] Add python-config.sh for use during cross compilation.

Changes by Ezio Melotti : -- nosy: +doko stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16235] Add python-config.sh for use during cross compilation.

Changes by Trent Nelson : -- nosy: +trent ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue16235] Add python-config.sh for use during cross compilation.

New submission from Ray Donnelly: Creates python-config.sh which aims to behave exactly the same as python-config except it doesn't depend on a Python interpreter on the build machine (only depends on a posixy shell, tested with bash, dash, MSYS-bash). I use this for cross compiling gdb with P