From mark at phillipsoasis.com Tue Jun 5 20:30:01 2007 From: mark at phillipsoasis.com (Mark Phillips) Date: Tue, 5 Jun 2007 11:30:01 -0700 Subject: [PythonCE] Very Basic Newbie Questions. Message-ID: <200706051130.02053.mark@phillipsoasis.com> I am starting a new project for mobile phones using the Windows Mobile Professional v 6 platform. The first target phone is the just released T-mobile Wing. This will be my first Windows Mobile app. However, I have successfully created Java based apps for phones using MIDP. I have a couple of questions regarding developing for the Windows mobile platform - 1. Do I need to develop on a Windows machine? I have developed my Java MIDP apps on Linux using an emulator for the phone. Can pythonce run on Linux? 2. Do I have to have a MS Development environment? If so, which one? 3. Any ideas if a python based app is faster than a Java based app for Windows Mobile phones? The processor on the Wing is somewhat limited in performance. Thanks for any thoughts or suggestions you can provide to help me start on my journey with pythonce! Mark Phillips mark at phillipsoasis.com From stewart at elkhornvalleypacking.com Fri Jun 15 17:47:57 2007 From: stewart at elkhornvalleypacking.com (Stewart Snyder) Date: Fri, 15 Jun 2007 09:47:57 -0600 Subject: [PythonCE] Build environment for PythonCE Message-ID: <4672B4AD.7090002@elkhornvalleypacking.com> Hello, I'm trying to write a small .dll extension for PythonCE for a Windows Mobile 2003 device; just something to allow me to use SHFullScreen, SIPShowIM, etc. I think I've got the environment mostly set up, but when I try using #include "Python.h" I get a series of 8 errors along the lines of "linkage specification contradicts earlier specification for 'asctime'", and the same again for ctime, clock, gmtime, and a few other time functions. These errors all originate from the armv4\time.h header file. My build environment is as follows: Microsoft eMbedded Visual C++ 4.0 Microsoft PocketPC 2003 SDK Python/PythonCE 2.5 source I assume I need to change a flag or compiler option somewhere, but I'm out of ideas for where to look. Anyone else know what I'm doing wrong? Thanks, Stewart From alexandre.delattre at enst-bretagne.fr Sat Jun 16 09:56:52 2007 From: alexandre.delattre at enst-bretagne.fr (alexandre.delattre at enst-bretagne.fr) Date: Sat, 16 Jun 2007 09:56:52 +0200 Subject: [PythonCE] Build environment for PythonCE Message-ID: <20070616095652.dmwfzzveo4s4og0c@webmail.enst-bretagne.fr> Hi Stewart, Maybe you should include python headers before the regular ones. To do so with evc4 : go to the menu Tools->Options, go to the tab Directories and choose include, then add an entry to the directory that contain python.h just before the regular includes. i've been able to compile a few extensions with a such config, for instance numarray, so I'm pretty sure this config is correct. Furthermore if you want to interface the SH* functions, you can also do so directly in python with ctypes, for instance : from ctypes import cdll; cdll.aygshell.SHFullScreen(...). For other example of such intefacing you can get a look at vensterce that uses the most common windows procedures. Alex. From stewart at elkhornvalleypacking.com Tue Jun 19 00:08:36 2007 From: stewart at elkhornvalleypacking.com (Stewart Snyder) Date: Mon, 18 Jun 2007 16:08:36 -0600 Subject: [PythonCE] Build environment for PythonCE In-Reply-To: References: Message-ID: <46770264.5080502@elkhornvalleypacking.com> Hi Alex, It looks like ctypes will do what I was interested in; I'm still looking at Venster itself. My main goal was to use an existing c++ library for some hardware on the units running PocketPC, and so far ctypes appears to let me do that. I also rechecked the order of the include directories like you said (also needed a directory entry for pyconfig.h), but was still running into the same errors. I suspect there's something wrong with the way I've got evc configured; but it seems irrelevant now, since I can compile DLLs fine without Python.h and still access their functions from Python. Thanks for the help! Stewart alexandre.delattre at enst-bretagne.fr > Date: Sat, 16 Jun 2007 09:56:52 +0200 > From: alexandre.delattre at enst-bretagne.fr > Subject: Re: [PythonCE] Build environment for PythonCE > To: pythonce at python.org > Message-ID: <20070616095652.dmwfzzveo4s4og0c at webmail.enst-bretagne.fr> > Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; > format="flowed" > > Hi Stewart, > > Maybe you should include python headers before the regular ones. > To do so with evc4 : go to the menu Tools->Options, go to the tab > Directories and choose include, then add an entry to the directory > that contain python.h just before the regular includes. > > i've been able to compile a few extensions with a such config, for > instance numarray, so I'm pretty sure this config is correct. > > Furthermore if you want to interface the SH* functions, you can also > do so directly in python with ctypes, for instance : from ctypes > import cdll; cdll.aygshell.SHFullScreen(...). > > For other example of such intefacing you can get a look at vensterce > that uses the most common windows procedures. > > Alex. > > > > ------------------------------ > > _______________________________________________ > PythonCE mailing list > PythonCE at python.org > http://mail.python.org/mailman/listinfo/pythonce > >