[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Akka & SWIG
- To: developer at arabeyes dot org
- Subject: Re: Akka & SWIG
- From: "Chahine M. Hamila" <mch at chaham dot com>
- Date: Thu, 21 Mar 2002 12:18:55 +0100
Mohammed Elzubeir a *crit :
> On Wed, Mar 20, 2002 at 01:33:42PM +0100, Chahine M. Hamila wrote:
> > Changing chonfigure is pretty trivial. Godd thing you pointed it out, if
> > you want we'll see together how the Python wrappers are done and I'll make
> > the SWIG support generic.
> > Salaam
> >
>
> As you may already know,
I didn't:)
> it's only a matter of using the same
> 'interface' file.. so something like,
>
> $ swig -o python_akka_wrap.c -python akka_module.c
> $ gcc $(CFLAGS) $(INC) -I/usr/include/python2.1 \
> -I/usr/lib/python2.1/config python_akka_wrap.c
>
> $ ld --shared $(LIBS) akka-module.o python_akka_wrap.o ... \
> -o python_akka_module.so
>
> $ python
>
> >>> import python_akka_module
> >>>
>
> and you are in business ;)
Tayeb, I will change chonfigure to make it flexible in that regard.
>
> Also, aside from the glib problem (which you know of), without an
> 'install' option w/ chonfigure, it makes the debian package a lot more
> of a hack than a clean package.
The glib problem is a macro problem. I have tried to solve it but since I am
not subject to the problem myself, I am not sure I fixed it. The best would be
that you take a look at the macro/ directory and take a look at the glib macro
yourself, it's very trivial. If I remember right Mohamd (Yosef?) already did
patch chonfigure for that too, so check the CVS version of chonfigure (or let
me check my mail in case I forgot to submit the patch).
As for the install option, we'll discuss it in private, as all is needed is as
I mentionned it before the scripts that make the creation of debian, rpm,
slackware packages automatic, or the instructions for an automatized install
(something like cp blablablabla) to integrate it in chonfigure.
>
> This goes very well for duali, if 'chonfigure' is not at a level where
> it can be _very_ flexible and already at a production level that is
> suitable for packaging, etc. then I am very much for going with the
> autotools (and don't worry, you don't have to learn m4 and company, I
> can take care of that) ;)
Chonfigure is way more flexible and easy to use than the autotools. Any effort
that you would invest on adding autotools support would be enough in fact to
add zillions of features to chonfigure. So we should see what the needs are and
write macros/extend/fix chonfigure in whatever way needed if it doesn't already
suit the needs.
Salaam,
Chahine