On 2 May 2014 09:21, Geert Janssens <janssens-ge...@telenet.be> wrote:
> ...
> It would be interesting to test with brancht 'maint' as well. The changes
> for libdbi 0.9.0 have been committed after 2.6.3 has been released.
>
> Also I'm confused here: are both versions (HEAD and 2.6.3) linking against
> libdbi 0.9 ? If so does the 2.6.3 build generate deprecation warnings for
> some libdbi functions ?

Compiling 2.6.3 the warnings were libdbi deprecations as you
suggested.  The warnings are gone in the maint branch., so that makes
sense.  The maint branch does not run, however, giving a SIGEGV in
dbi_initialize_r().

I am confused by the fact that if I compile the 2.6.3 tarball (on the
same system) then I do not get the deprecation warnings.

> ....
> John's recent c++ related commits have caused sufficient difference between
> the stable branch (maint and by extension also tag 2.6.3) and HEAD that you
> need to start from a completely clean build directory AND have to rerun
> autogen.sh in between. So the steps would become:
>
>
>
> sudo make uninstall (to remove your installed version of gnucash)
>
> make maintainer-clean (wipes everything that was generated)
>
>
>
> git checkout 2.6.3 (or git checkout maint)
>
>
>
> ./autogen.sh
>
> ./configure ...
>
> make
>
> sudo make install
>
>
>
> Because I switch a lot between maint and master, I have chosen to clone the
> gnucash repository twice. One close is permanently checked out to maint the
> other to master.
>
>
>
> And in addition I'm building in separate build directories instead of in the
> source directories. That makes it easier to start from scratch (just delete
> the build directory). This is pretty easy to do:
>
> create your build directory (wherever you like)
>
> cd <build-directory>
>
> <path-to-gnucash-configure>/configure ...
>
> make

Thanks for all that, it all makes sense.

Colin
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Reply via email to