Gnucash - Diane Trout

Page Summary

Links

Gnucash

I feel like I'm completely bonkers trying to rework gnucash to use mono on OS X.

I made some progress converting the automake/autoconf stuff to CMake, it still doesn't remotely compile, but at least its trying to compile the engine. (It's currently looking for config.h, which since I didn't use autoconf is obviously missing).

I know I have trouble finishing things, but I do really want gnucash back and I do want to be able to interact with it from a language other than scheme which does provide a bit of motivation. (Though instead of using mono, I wonder if it'd be easier to parse scheme code with python).

(no subject)

w.r.t. gtk+-macox.... interesting. I wonder how complete that is, and how many of the dependencies it provides.

I'm not at all sure why you ported from autotools to cmake.. But honestly, if you want to get gnucash working with gtk+-macosx I can guarantee you that the gnucash developement team would be interested in your help and your patches would be gladly accepted.

Note, however, that porting to cmake doesn't count here. The auto tools work just fine. :-D

If you're interested in following up on this topic, I suggest you join the gnucash-devel@gnucash.org mailing list and bring up the topic there!

Note, however, that porting to cmake doesn't count here. The auto tools work just fine. :-D

I might quibble with the "just fine" part of that. Autotools were a great idea, they demonstrated how auto-configuration is exceedingly useful in creating portable code. However it's my opinion that autotools has gotten old, creaky, and quite crufty, and now needs to die. (As a python programmer, I kind of wish that scons had won out, but CMake works, is reasonably fast, and has picked up some momentum.)

CMake scripts can be read without knowing portable korn/bash shell and M4

The CMake configuration language is pretty easy to pick up.

CMake provides a standardized way of viewing and fixing incorrectly auto-detected variables

Not only does CMake work on unix like systems it also runs on windows, without cygwin

For IDE people CMake can generate KDevelope, XCode and Visual Studio files in addition to standard makefiles

CMake includes support for defining, building, and running tests

Though I do wish that CMake macros were real functions with real namespaces and not just a macro language. Also kitwares business model is, give away software, sell a book, so the documentation is a bit sparse. Though with KDE's adoption of CMake the freedocs are getting much better.