Xavier de Gaye added the comment: > I don't think that identifying the target by some path is the right way to > go, and you should be able to identify the target by giving the target > triplet as used by the configure parameters and then deduce the location from > the target (or have an explicit location given). > > The idea here is to use the platform identifier which we already had in the > trunk before the PLATDIR was removed (the multiarch id or if not defined the > platform). So by having a <target> specifier, you could deduce a path, or a > <target>-python-config executable and you're done. No need to know about a > path directly. Of course python cross builds would have to install the > <target>-python-config executable or symlink.
Hum, you still need to provide the native python interpreter with the _path_ to the <target>-python-config executable that can be anywhere on the file system (its location is relative to the cross compiled build, not the native interpreter), so it seems that this contradicts your previous sentence saying "I don't think that identifying the target by some path is the right way to go". ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28833> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
