Re: glib compile bug?
- From: "David Necas (Yeti)" <yeti physics muni cz>
- To: gtk-list gnome org
- Subject: Re: glib compile bug?
- Date: Sun, 26 Mar 2006 18:57:58 +0200
On Sun, Mar 26, 2006 at 10:51:23AM -0600, digitek wrote:
> > <snip>
> >
> > Hrm.. g_value_take_string is indeed in the 2.2.3 source wtf?
> >
> > [root localhost gtk]# cat glib-2.2.3/gobject/gmarshal.c | grep
> > g_value_take_string
> > g_value_take_string (return_value, v_return);
>
> scratch that...something else is creating that
> file. What is going on with my glib compile? Is it
> writing gmarshal.c on the fly?
Yes, it is generated -- see the makefile. Normally it uses
./glib-genmarshal, but for cross-compilation it tries to
find it in PATH. This makes sense as it cannot run the
cross-compiled ./glib-genmarshal, but you have to give it
some glib-genmarshal that grenerates an output the compiled
version of GLib undestands.
Yeti
--
That's enough.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]