[capi-sig] Python for VxWorks

nachaat hassis nachaat05 at yahoo.fr
Mon Feb 17 09:26:08 CET 2014

Hi Gary,
I was trying to port Python 3.0 at first .. after porting it, i noticed that Twisted and Buildbot support only Phyton 2.7
So i had to port Python 2.7 ..
I was working with VxWorks 6.9 as well (ARM)..
well, after trying to port the Python as a DKM, i had it working but i had many problems with Twisted and Buildbot .. (they use many signals, pipes, ..) many POSIX stuff .. 
So i took another direction and tried to make it run as an RTP.
With the RTP-Version i had a better result. POSIX stuff is working, my buildbot and twisted are working (with few changes since fork and exec are not supported for example) ..
But i made it work .. I have the feeling that the Python-Interpreter was more stable as a DKM but maybe its just an impression ..

I had the loadable shared objects part done aswell .. If you need help with this part, just ask .. 

and thanks for the replay.

Best regards ..

Gary Kenaley <gkenaley at yahoo.com> schrieb am 22:00 Samstag, 15.Februar 2014:
nachaat hassis <nachaat05 at ...> writes:

> Hi Everybody, 
> im trying to port Python on VxWorks or to find binarys for VxWorks.
> My search on the internet was not very successfull till now.
> In this
page http://docstore.mik.ua/orelly/other/python/0596001886_pythonian-chp-2-sect-2.html you
> can read:
> The site http://www.python.org/download/ provides links to binary
distributions for Macintosh,
> OS/2, Amiga, RISC OS, QNX, VxWorks, IBM AS/400, Sony PlayStation 2, and
Sharp Zaurus.
> >
> but i cant find any binarys for VxWorks there.
> Is it even possible to port Python on VxWorks? lets say 2.7 ..
> The version is not very important to me .. i just need someone to point me
to the right direction ..
> An old binarys of Python for VxWorks would do it..
> Did someone hear that anybody ported Python on Vxworks?
> My goal is to make BuildBot run on VxWorks ..
> Best regards.


I am currently working on a Python 2.7 for VxWorks 6.9.3 x86 user space.
The best resource is: http://wiki.osdev.org/Porting_Python
I am using User Space Real Time Processes (RTPs) because they have POSIX
PSE52+ functionality and full memory protection.
I had the basic 2.6.1 interpreter running this way, but it's fairly useless
without the loadable shared objects (the osdev site should help a lot with
those cross build aspects).

If I get it working satisfactorily, I will post back.


capi-sig mailing list
capi-sig at python.org

More information about the capi-sig mailing list