ccmtools-devel

[ccmtools-devel] python wrapper status

[Leif J. <le...@am...>]

Hi all -

I'm still hacking on the Python wrapper generator. It's a bit slow
going, but progress is happening. I think the wrappers will be really
clean when they're finished ; there is a nice mapping between Python
objects and the CCM component structure, at least so far. The big issue
is going to be converting interfaces to Python and back---eech.

I made a couple of changes to the C++ generators. Notably, the base
CppGenerator class now has a list called base_namespace that can hold
any base namespaces needed by the child classes. For the
CppLocalGeneratorImpl, this list holds [ "CCM_Local" ], for the remote
generators it could hold [ "CCM_Remote" ], and for the
CppPythonGeneratorImpl it holds [ "CCM_Test", "Python", "CCM_Local" ].

These base namespaces are added to the namespace stack when the code
generators start processing a graph, so we (hopefully) don't need as
many hacks in the handleNamespace function (which is kind of a hack
anyway ; that's what you get for having a Python coder design things for
you. :).

leif

--
Leif Morgan Johnson : http://ambient.2y.net/leif/

Re: [ccmtools-devel] python wrapper status

[Joerg F. <jf...@sa...>]

>>>>> "Leif" == Leif Johnson <le...@am...> writes:

Leif> I'm still hacking on the Python wrapper generator. It's a bit slow
Leif> going, but progress is happening. I think the wrappers will be really
Leif> clean when they're finished ; there is a nice mapping between Python
Leif> objects and the CCM component structure, at least so far. The big issue
Leif> is going to be converting interfaces to Python and back---eech.

I'm not sure if I mentioned this already. In the wx-utils package that
you can download from http://sourceforge.net/projects/confix, there is
a glue module ext-python that you can use to automatically pull in the
Python include path and library.

The module is referred to in section "Using Third Party Libraries"
where there is explained what the glue code does.

Joerg

Re: [ccmtools-devel] python wrapper status

[Leif J. <le...@am...>]

Hi Joerg !

On Fri, 12 Dec 2003, Joerg Faschingbauer wrote:

> >>>>> "Leif" == Leif Johnson <le...@am...> writes:
> 
> Leif> I'm still hacking on the Python wrapper generator. It's a bit slow
> Leif> going, but progress is happening. I think the wrappers will be really
> Leif> clean when they're finished ; there is a nice mapping between Python
> Leif> objects and the CCM component structure, at least so far. The big issue
> Leif> is going to be converting interfaces to Python and back---eech.
> 
> I'm not sure if I mentioned this already. In the wx-utils package that
> you can download from http://sourceforge.net/projects/confix, there is
> a glue module ext-python that you can use to automatically pull in the
> Python include path and library.

My current approach has been to use an EXTERNAL_LIBRARY call in a
Makefile.py. This, like the Mico issue, has the problem of hard coding a
version number in the external library call (does the developer have
python 2.2 or 2.3 headers---or maybe even 1.5 ?). But for the moment it
will have to do.

Is there any way we could hack up Confix to accept a list of include
directories to search for a provided header file ? (Does it do this
already ?) But even this isn't a great solution, since developers might
have stuff installed in all sorts of nonstandard locations.

Ahh, standardization ... how easy and boring things would be.

leif

--
Leif Morgan Johnson : http://ambient.2y.net/leif/

Re: [ccmtools-devel] python wrapper status

[Joerg F. <jf...@sa...>]

>>>>> "Leif" == Leif Johnson <le...@am...> writes:

Leif> Hi Joerg !
Leif> On Fri, 12 Dec 2003, Joerg Faschingbauer wrote:

>> >>>>> "Leif" == Leif Johnson <le...@am...> writes:
>> 
Leif> I'm still hacking on the Python wrapper generator. It's a bit slow
Leif> going, but progress is happening. I think the wrappers will be really
Leif> clean when they're finished ; there is a nice mapping between Python
Leif> objects and the CCM component structure, at least so far. The big issue
Leif> is going to be converting interfaces to Python and back---eech.
>> 
>> I'm not sure if I mentioned this already. In the wx-utils package that
>> you can download from http://sourceforge.net/projects/confix, there is
>> a glue module ext-python that you can use to automatically pull in the
>> Python include path and library.

Leif> My current approach has been to use an EXTERNAL_LIBRARY call in a
Leif> Makefile.py. This, like the Mico issue, has the problem of hard coding a
Leif> version number in the external library call (does the developer have
Leif> python 2.2 or 2.3 headers---or maybe even 1.5 ?). But for the moment it
Leif> will have to do.

Leif> Is there any way we could hack up Confix to accept a list of include
Leif> directories to search for a provided header file ? (Does it do this
Leif> already ?) But even this isn't a great solution, since developers might
Leif> have stuff installed in all sorts of nonstandard locations.

Leif> Ahh, standardization ... how easy and boring things would be.

Yeah, isn't variability great?

The autoconf thing in wx-utils/ext-python module does what you
want. The Python interpreter that is found in your path
(AM_PATH_PYTHON does that) is asked for its install prefix, and the
locations of headers and libraries are deduced from that.

Joerg