[PythonCE] Build environment for PythonCE

[Stewart Snyder]

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
>
>