From: Andy Wingo <wingo@pobox.com>
To: guile-gtk@sources.redhat.com
Subject: Re: guile-gobject problem
Date: Fri, 15 Aug 2003 13:19:00 -0000 [thread overview]
Message-ID: <20030815130928.GA926@lark> (raw)
In-Reply-To: <87llu0vsx8.fsf@alice.rotty.yi.org>
There've been some internet difficulties at my workplace, but hopefully
they're sorted out now...
On Mon, 11 Aug 2003, Andreas Rottmann wrote:
> | DSTWService* <dstwservice*>
> | gboolean <gboolean>
> | GType <gtype>
> | char* <char*>
> | none <none>
> | gunichar* <gunichar*>
Hmm, looks like you forgot to set the standard wrapset as a used
wrapset. Check the gw-atk-spec.scm for more details, bit it will suffice
to add (gw:wrapset-depends-on ws "guile-gnome-gw-standard") to your
wrapset definition code.
Of course, you have to also depend on glib and gobject if you want those
types to be recognized as well.
Regards,
wingo.
next prev parent reply other threads:[~2003-08-15 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 20:30 Andreas Rottmann
2003-08-12 14:49 ` guile-gobject problem [solved], g-wrap Andreas Rottmann
2003-08-12 15:29 ` Greg Troxel
2003-08-12 16:31 ` Andreas Rottmann
2003-08-12 17:00 ` Rob Browning
2003-08-15 13:19 ` Andy Wingo [this message]
2003-08-15 13:58 ` guile-gobject problem Andreas Rottmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030815130928.GA926@lark \
--to=wingo@pobox.com \
--cc=guile-gtk@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).