From helan4258+nabble at gmail.com Wed Jan 14 20:03:15 2009 From: helan4258+nabble at gmail.com (helan4258) Date: Wed, 14 Jan 2009 11:03:15 -0800 (PST) Subject: [PythonCE] Numarray Message-ID: <21447785.post@talk.nabble.com> Hi! I am a newbie to pythonce. Installation of pyce2.5-smartphone on my blackjack is fine but without further patch(don't know how to make it work!). I am going to set up the numarray package, however, cannot get the door in. Unlike desktop edition, it looks like lacking of the set up file. Or any stuff i was miss? Appreciate any help, thanks a lot! helan -- View this message in context: http://www.nabble.com/Numarray-tp21447785p21447785.html Sent from the Python - pythonce mailing list archive at Nabble.com. From eckhardt at satorlaser.com Fri Jan 23 10:19:39 2009 From: eckhardt at satorlaser.com (Ulrich Eckhardt) Date: Fri, 23 Jan 2009 10:19:39 +0100 Subject: [PythonCE] Update on MS Windows CE port Message-ID: <200901231019.39111.eckhardt@satorlaser.com> Hi! Just a short update on my porting issues. I tried various things in the holidays/vacation, filed several bug reports, got a few patches applied and I think the thing is taking shape now. However, I couldn't work on it for the past two weeks since I'm just too swamped at work here. I haven't given up though! What still needs work? The main component that requires porting is the pythoncore project, but that port isn't finished yet. I'm using the VS8.0 project files as a base and adapted it in the following steps (note that this is preliminary): 0. Check out trunk (i.e. 2.x, not 3.x). 1. Create new project configuration for your CE target and use the win32 one as a base. 2. In the preprocessor settings, add these entries: UNICODE,_UNICODE,UNDER_CE,_WIN32_WCE=$(CEVER) 3. Try compiling. ;) What issues are left? There are two classes of errors you will encounter, those that are related to CE itself (like missing errno and other parts of standard C) and those that are more general, like assuming TCHAR=char. Those that assume that TCHAR=char can also be found with the plain win32 variant by simply adding UNICODE and _UNICODE to the preprocessor defines. What are the future plans? I'm trying to fix errors in pythoncore one by one and provide separate bug reports with patches. Note that there are already several patches in the BTS which would merit reviews if you have time, even if it's only a "patch applies and doesn't cause regressions". When I get pythoncore to compile (and be it by disabling a few builtin modules), I will try to get the commandline interface to work. Note that IIRC there are two commandlines availabel under CE, one is a common cmd.exe, the other is called AYGShell or some such. Both will/might require different approaches. Another problem is the fact that there is not just one target platform but a potentially infinite number of them, since every CE device can have a separate SDK which further might provide different features. This probably requires autogenerated build files or some other autoconf-like procedure that allows enabling or disabling certain features for builds. so much for now Uli -- Sator Laser GmbH Gesch?ftsf?hrer: Thorsten F?cking, Amtsgericht Hamburg HR B62 932 ************************************************************************************** Sator Laser GmbH, Fangdieckstra?e 75a, 22547 Hamburg, Deutschland Gesch?ftsf?hrer: Thorsten F?cking, Amtsgericht Hamburg HR B62 932 ************************************************************************************** Visit our website at ************************************************************************************** Diese E-Mail einschlie?lich s?mtlicher Anh?nge ist nur f?r den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empf?nger sein sollten. Die E-Mail ist in diesem Fall zu l?schen und darf weder gelesen, weitergeleitet, ver?ffentlicht oder anderweitig benutzt werden. E-Mails k?nnen durch Dritte gelesen werden und Viren sowie nichtautorisierte ?nderungen enthalten. Sator Laser GmbH ist f?r diese Folgen nicht verantwortlich. **************************************************************************************