Re: simple and easy way - gmmproc to wrap a single gobject?

[Murray Cumming <murrayc murrayc com>]

On Thu, 2008-07-31 at 21:52 +0200, Milosz Derezynski wrote:
> I'm also studying gmmproc at the moment in order to allow us the
> wrapping of specific GStreamer elements for gstreamermm.
> 
> In order to do what you want, you will unfortunately need not only the
> m4 files, which (for plain GObject stuff) glibmm installs into
> $libdir/glibmm-$VERSION/proc/m4, and gtkmm installs its into
> $libdir/gtkmm-$VERSION/proc/m4, but also the installed .defs, which
> neither doesn't install at the moment (i've changed gstreamermm to
> install its defs into $libdir/gstreamermm-$VERSION/proc/defs).

I don't see the point of installing .defs files.

> Assuming you  _have_ the defs somewhere, for example in
> $libdir/glibmm-$VERSION/proc/defs (e.g. /usr/lib/gibmm-2.4/proc/defs),
> you can convert a single object, for example with input files
> 'myobjectclass.hg' and 'myobjectclass.ccg' like this:
> 
> /usr/lib/glibmm-2.4/proc/gmmproc -I /usr/lib/glibmm-2.4/proc/m4
> --defs /usr/lib/glibmm-2.4/proc/defs/ myobject . .
> 
> There is another problem that AFAIK right now (i might be wrong), you
> can specify only one m4 directory at any given time,

If that's true then it should be easy to fix.

>  perhaps the glibmm one is searched by default, i'm not sure right
> now; i didn't try the above like with a _gtk_ class, only with
> glib-only code (i assume it does look for the glibmm m4's by default
> though because the above line works for a single gstreamermm class).
> 
> The . and . at the end of the command line mean that the input dir
> will be the output dir (i.e. .h and .cc will be created where .hg
> and .ccg are).
> 
> You can get the defs from the glibmm source tarball, in
> $top_srcdir/glib/src/*.defs

These are only useful for generating glibmm's source code. Why would
they be useful for generating any other source code?

> 
-- 
murrayc murrayc com
www.murrayc.com
www.openismus.com