John Ralls wrote:
By the way, why does 3.0 start up with:
"This is a development version. It may or may not work."
Did you build 3.0 from a git checkout or from a tarball? It’s only supposed to
print that message when you build from git...
Built from tarball downloaded from Sourceforge.
> On Apr 2, 2018, at 5:59 PM, lj wrote:
>
> John Ralls wrote:
>>> ...
>>> (Should I write this up at bugzilla.gnome.org ?)
>> Sure.
>> We should be be using CMAKE_INSTALL_FULL_SYSCONFDIR to set the path so that
>> it always works no matter what cmake does with it, and cmake’s unique
>> understa
John Ralls wrote:
...
(Should I write this up at bugzilla.gnome.org ?)
Sure.
We should be be using CMAKE_INSTALL_FULL_SYSCONFDIR to set the path so that
it always works no matter what cmake does with it, and cmake’s unique
understanding of the gnu coding standard leads it to do some strange th
> On Apr 1, 2018, at 6:03 PM, lj wrote:
>
> Using: gnucash-2.7.8(unstable) on 32-bit Slackware Linux 14.2
>
> I built gnucash-2.7.8 (unstable) to be installed at /opt/gnucash. I used
> a cmake line that included:
> -D CMAKE_INSTALL_PREFIX=/opt/gnucash
>
> After build and install, gnucash wou
Using: gnucash-2.7.8(unstable) on 32-bit Slackware Linux 14.2
I built gnucash-2.7.8 (unstable) to be installed at /opt/gnucash. I used
a cmake line that included:
-D CMAKE_INSTALL_PREFIX=/opt/gnucash
After build and install, gnucash would not start. First error was unable to
find schemas, whic
