#Gnucash source code how to#
#Gnucash source code update#

#Gnucash source code update#

Update the relevant sections in Help Manual and the Concept Guide.Try to keep the README files and that in src/doc up to date.not static) functions are documented with Doxygen-formatted comments. If your code adds or changes some functionality, do not forget the documentation. Be sure that make check passes before preparing your patch or pushing your commit.If your code will contain textual output for the user, have a look at Translation: Tips for Developers and configuration Settings Wording.Please try to develop according to Test Driven Development principles, following our Testing guidelines.You can follow the git instructions for cloning the repository and preparing patches.īuild instructions for various platforms are described or linked at Building.

Read the two files HACKING and README.git Some of the team also hang out on IRC so you can interact more directly. Please subscribe to the Mailing Lists and introduce yourself to the development team.

If you prefer to dive in at the deep end, have a look at the development team's long-term plans.

It's an excellent way to get familiar with the code base and to introduce yourself to the team.

Patches to fix bugs are always a appreciated.

We have updated the GUI to Gtk+-3 in the 2.7 series. The next development cycle will include migrating those parts of Gnucash other than the GUI to C++ see our C++ page for details and resources.

#Gnucash source code how to#

Understanding how to use that is an important skill to developing for GnuCash. Some of it uses GObject, some uses a home-grown GObject-like system called QofObject, and some just does what GObject does in straight C. Most of the code is written in an object-oriented style. Note that these documents have a separate repository. The Help Manual and Concepts Guide are formatted using DocBook, an SGML markup language which enables us to publish them in several formats. Details about our use are on the Doxygen wiki page. We use Doxygen to document the sources, including the C API. Understanding this complex system isn't generally necessary for fixing simple bugs, but more complex work will. The C API is wrapped for Guile access with SWIG Python wrappers can be created with a configure option. A Guile interpreter is built in and parts of Gnucash-principally reports, but also parts of the user configuration, file import, and other small parts-are in Scheme.