When I ported Stackless Python to Sony PSP, I followed the same approach Richard exposed.
The tricky part is the tasklet switching code where some assembly code is needed, but since most WinCE are ARMs, maybe you can use any of the available tidbits with minor modifications. Carlos On Mon, Dec 8, 2008 at 10:17 AM, Richard Tew <[EMAIL PROTECTED]> wrote: > On Mon, Dec 8, 2008 at 5:30 AM, Mads Darø Kristensen <[EMAIL PROTECTED]> > wrote: >> I am currently in the process of porting Stackless Python 2.5 to run on >> Windows CE/Mobile devices and I would like some advise before I waste too >> much precious time :-) >> >> What I have done is this: >> 1) I have fetched the source code of Python 2.5, PythonCE 2.5, and Stackless >> Python 2.5 >> 2) I have created a diff of Python vs. PythonCE (diff -uNr Python-2.5 >> Python-2.5-wince) >> 3) I have applied that diff as a patch to the Stackless Python checkout >> 4) I am currently going through the tings that failed during that patch to >> see if I can get it to work... >> >> Is this the right way to do a Stackless port? Am I missing something? > > Well, I personally would diff the stackless 2.5 against Python 2.5. > Then apply those changes to the PythonCE. But, whatever works best > for you. > > I would expect the Stackless changes to be more minimal than the > Python CE changes as most of the Stackless code is in the Stackless > sub-directory and there are only minimal changes to the main Python > code. > > Cheers, > Richard. > > _______________________________________________ > Stackless mailing list > [email protected] > http://www.stackless.com/mailman/listinfo/stackless > -- ------------------------------------------------------------------- Visit Stackless Examples Project http://code.google.com/p/stacklessexamples/ Stackless Python - www.stackless.com ------------------------------------------------------------------- _______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
