On Tuesday 16 August 2005 3:45 pm, Derek Atkins wrote: > Quoting Neil Williams <[EMAIL PROTECTED]>: > > The guile bindings at this stage would only be removed from the *test* > > routines - I won't change the structure of the actual modules until > > you've had a chance to test my proposed patch. > > Yea.. that seems to make sence to me.. At least from within the QOF > code. Even once it's spun out the scheme bindings should still be > tested from > GnuCash.
Yes - e.g. I won't change the test-load type routines but then those won't be in either QOF or CashUtil. > Oh. I see. yea, this should probably be fixed.. Unless we change the > pricedb > to be a QOF object ;) I'd thought of that, hadn't got around to it yet. It's a little different as there is only one db per book, unlike other objects. > > My patch today includes temporary #ifdef rules so that CashUtil can build > > the file without the customised QofBackend struct. Those will be removed > > later. > > *sigh* We do have a lot of special-casing, don't we? :( Definitely. :-( > > So it produces no guile or g-wrap dependencies? Will it run on a base > > system, something that say only has the CLI version of emacs? Are there > > systems with Glib but without scheme? > > There is a build-time dependency on /usr/bin/guile. There is no dependency > on g-wrap, and there is no runtime dependency on either guile OR g-wrap. Fine, that's that one solved. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
pgp9qF8R1RUyx.pgp
Description: PGP signature
_______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
