David Hampton <[EMAIL PROTECTED]> writes:

> I'm currently working on the gtk2 port of gnucash, and as part of the
> effort am trying to remove all of the really old dependencies in
> gnucash.  I'd like to update the g-wrap requirement from 1.3.4 to 1.9.x
> but have run into a problem.  I completely removed 1.3.4 from my system,
> and I can compile against 1.9.x but the resulting code won't run.  The
> error message is:
>
>       ERROR: no code for module (g-wrap gw-wct)
>
> This is the same problem Greg Troxel reported last November.  The error
> appears to be a direct result of a line in our g-wrap specification
> files.  Do all our specification files need to be updated?  If so, is it
> just the use-modules statements or will the whole file (all 12 of them)
> need to be rewritten?  One of the gnucash developers thought there was a
> backward compatibility mode in 1.9 that could handle 1.3 spec files.
> Would be nice if it exists.  Anyway, I couldn't find anything about
> converting 1.3 -> 1.9 in the documentation, so anything you can tell me
> will help.  Thanks.
>
What exact version of G-Wrap did you use? This should beeen fixed
since a while now - Gnucash should build/work with 1.9 as-is.

> David
>
> P.S. Should g-wrap 1.3 be parallel installable with 1.9?
>
Yes and no. The runtime is parallel-installable, so you can keep
applications/libraries built with 1.3 installed when upgrading G-Wrap
to 1.9, but the development environment is not. This is not a problem
however, due G-Wrap 1.9 provides compatibility with 1.3.

Cheers, Rotty
-- 
Andreas Rottmann         | [EMAIL PROTECTED]      | [EMAIL PROTECTED] | [EMAIL 
PROTECTED]
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62
v2sw7MYChw5pr5OFma7u7Lw2m5g/l7Di6e6t5BSb7en6g3/5HZa2Xs6MSr1/2p7 hackerkey.com

Make free software, not war!


_______________________________________________
g-wrap-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/g-wrap-dev

Reply via email to