python-bindings: coredump whil executing gnucash.Session

John Ralls jralls at ceridwen.us
Sun Dec 14 23:34:08 EST 2014


> On Dec 14, 2014, at 7:18 PM, Mike Alexander <mta at umich.edu> wrote:
> 
> --On December 14, 2014 at 7:02:15 AM -0800 John Ralls <jralls at ceridwen.us> wrote:
> 
>> Did you regenerate the swig files? You'll need to do that often on
>> master. If you build in a separate directory you'll need to `git
>> clean -fdx` in your source directory then re-run autogen.sh and
>> configure. If you build in-source `make distclean` should do it.
> 
> Is that really true?  I've been building in a separate build directory for years and haven't ever done that.  If I want a clean build I just move the existing build directory aside and create a new one.  This has always seemed to work.  It appears to me that the generated swig C source files are put in the build directory, not the source directory, so blowing away the build directory causes them to be rebuilt.  If you build in the source directory a 'make distclean' is no doubt required.

Well, I thought that there were swig products written into $srcdir, but I just looked and I don’t see any. So it seems that simply doing `make distclean` or `rm -rf *` in a build directory will do the job. 

Regards,
John Ralls




More information about the gnucash-devel mailing list