bpo-31904: Add cross-build support for VxWorks RTOS - #11968
Conversation
|
I have made the requested changes; please review again |
|
Thanks for making the requested changes! @vstinner: please review the changes made to this pull request. |
vstinner
left a comment
There was a problem hiding this comment.
LGTM except of 2 minor changes: please fix NEWS entry and variable name.
| return sys.platform | ||
| host_platform = get_platform() | ||
|
|
||
| _vxworks = ('vxworks' in host_platform) |
There was a problem hiding this comment.
Please rename the variable to VXWORKS to better distinguish local and global variables in functions below.
By the way, I would also prefer to rename host_platform to HOST_PLATFORM for the same reason, but it should be done in a separated PR.
There was a problem hiding this comment.
Just to confirm: all the variables that are not supposed to be modified should be defined as constants, right? If this is true, besides host_platform, cross_compiling is another one to fix. I looked through PEP-8 but didn't find the guidance.
Out of curiosity, does CPython run LGTM analysis as well? |
Are you talking about lgtm.com? I know that Mark Shannon is working for this company, and I know that CPython is scanned by lgtm.com. Sadly, I never looked at it. |
Ah, I found it: https://lgtm.com/projects/g/python/cpython/ |
|
Thanks @pxinwr, I merged your PR ;-) |
|
|
|
|
|
|
|
I wrote PR #12068 as a follow-up of this PR. |

This PR enables cpython build system to cross-build for VxWorks RTOS. More and full support on modules for VxWorks will continuously be added by the coming PRs.
VxWorks is a product developed and owned by Wind River. For VxWorks introduction or more details, go to https://www.windriver.com/products/vxworks/
Wind River will have a dedicated engineering team to contribute to the support as maintainers.
We already have a working buildbot worker internally, but has not bound to master. We will check the process for the buildbot, then add it.
https://bugs.python.org/issue31904