bpo-31904: Add support for VxWorks RTOS by pxinwr · Pull Request #11951 · python/cpython (original) (raw)

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation3 Commits26 Checks0 Files changed

Conversation

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

pxinwr

This PR enables cpython to cross-build on VxWorks RTOS. As part of the whole effort, this PR only aims at achieving some basic support including most of built-in modules, os and subprocess modules. More and full support will continuously 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

@hliu0 @pxinwr

The main reason are:

  1. The locale is frequently misconfigured.
  2. Missing some functions to deal with locale in VxWorks C library.

@wyxin1008 @pxinwr

@kuhlenough @pxinwr

@jianxu3 @pxinwr

Redefine autoconf m4 macro for:

  1. Passing compiler check
  2. Passing lib and function search check

@jianxu3 @pxinwr

Modify configure.ac for VxWorks and generate new configure

@hliu0 @pxinwr

@pxinwr

@jianxu3 @pxinwr

…ompiler driver, python doesn't need that changes after switching to use the compiler driver.

@jianxu3 @pxinwr

@yuesun1 @pxinwr

@LihuaZhao @pxinwr

@LihuaZhao @pxinwr

@yuesun1 @pxinwr

@hliu0 @pxinwr

@wyxin1008 @pxinwr

@wyxin1008 @pxinwr

@jianxu3 @pxinwr

@jianxu3 @pxinwr

@jianxu3 @pxinwr

@wyxin1008 @pxinwr

@jianxu3 @pxinwr

@wyxin1008 @pxinwr

@wyxin1008 @pxinwr

@yuesun1 @pxinwr

@the-knights-who-say-ni

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for your contribution, we look forward to reviewing it!

@pxinwr

@pxinwr

@vstinner

This PR is too big, it must be splitted into smaller parts:

I'm interested to review the first one, UTF-8/encoding changes ;-)

@pxinwr

This PR is too big, it must be splitted into smaller parts:

* UTF-8 encoding

* subprocess + _vxapi module

* time changes: clock, mktime, etc.

* other misc changes: DELIM, configure, etc.

I'm interested to review the first one, UTF-8/encoding changes ;-)

OK. I will close this big one and split it into several smaller ones. Thanks for your comments.