Re: [GNC-dev] gnc_add_swig_guile_command compile errors

Just to confirm with build-cmake in the gnucash-3.0 toplevel folder using any of .. ../ ../../gnucash-3.0 as the argument for Cmake will work as expected. - David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html

[GNC-dev] guile error during build

This message had the subject "Building GnuCash 3 on openSuSE". May be that did not raise enough attention ... So, any hints from anybody with more scheme knowledge is greatly appreciated. Hi! I did not build GnuCash myself for some time, but with 3.0 I did try again. I'm running openSUSE

Re: [GNC-dev] gnc_add_swig_guile_command compile errors

Dave, The info about directories being separate is higher up that wiki page in the Cmake section. I too missed it not long ago trying to build the 2.7 series. Perhaps the page needs to be re-organized or maybe inside that Ubuntu section, it needs to be made clear that the higher general

Re: [GNC-dev] running setup-mingw64.ps1

Hi again, I tried this at home and did not get the above errors. I did however get problems on install, and problems after install. The install problems are that some package installs appear to fail eg: (57/97) installing texinfo 1 [main] pacman 4232 fork: child -1 - forked process 9808

Re: [GNC-dev] GnuCash 2.6.20 Released

> On Apr 8, 2018, at 10:47 AM, Mark Cochran wrote: > > Fedora 27, using MariaDB 10.2.14 backend, with gnucash database on one host. > gnucash 2.6.20 rev 972647d2d > I get as far as "Loading data..." on the spash screen, then > 'GnuCash could not complete a critical

Re: [GNC-dev] guile error during build

Hi John, Am 08.04.2018 um 18:45 schrieb John Ralls: On Apr 8, 2018, at 3:04 AM, Herbert Thoma wrote: This message had the subject "Building GnuCash 3 on openSuSE". May be that did not raise enough attention ... So, any hints from anybody with more scheme

Re: [GNC-dev] Gnucash-3.0 build error: GTEST not found

> On Apr 7, 2018, at 11:12 PM, DaveC49 wrote: > > Hi, > > I am past the initial problem but I appear to be having a problem with GTEST > not being found. I have gtest 1.8.0 intsalled and I have also uninstalled > it and reinstalled 1.7.0 from the ubuntu repository

Re: [GNC-dev] guile error during build

> On Apr 8, 2018, at 3:04 AM, Herbert Thoma > wrote: > > This message had the subject "Building GnuCash 3 on openSuSE". > May be that did not raise enough attention ... > > So, any hints from anybody with more scheme knowledge is greatly > appreciated. > >

Re: [GNC-dev] GnuCash 2.6.20 Released

Fedora 27, using MariaDB 10.2.14 backend, with gnucash database on one host. gnucash 2.6.20 rev 972647d2d I get as far as "Loading data..." on the spash screen, then 'GnuCash could not complete a critical test for the presence of a bug in the "libdbi" library.' trace file shows * 11:40:25 

Re: [GNC-dev] running setup-mingw64.ps1

> On Apr 8, 2018, at 8:10 AM, pjlbyrne wrote: > > Hi again, > > I tried this at home and did not get the above errors. > > I did however get problems on install, and problems after install. > > The install problems are that some package installs appear to fail eg: >

Re: [GNC-dev] [GNC] GnuCash 2.6.20 Released

On 04/08/2018 12:06 PM, John Ralls wrote: On Apr 8, 2018, at 10:47 AM, Mark Cochran wrote: Fedora 27, using MariaDB 10.2.14 backend, with gnucash database on one host. gnucash 2.6.20 rev 972647d2d I get as far as "Loading data..." on the spash screen, then 'GnuCash

[GNC-dev] Gnucash-3.0 build error: GTEST not found

Hi, I am past the initial problem but I appear to be having a problem with GTEST not being found. I have gtest 1.8.0 intsalled and I have also uninstalled it and reinstalled 1.7.0 from the ubuntu repository with the same result: $ cmake -D CMAKE_INSTALL_PREFIX=/usr/local/gnucash -D

Re: [GNC-dev] Register + Unicode (was Re: emojis everywhere...)

On Sat, Apr 07, 2018 at 08:20:35PM -0700, John Ralls wrote: > Depends on what you see as the bug. The bug is the inconsistency. I have opinions, for what they're worth, on how it should behave: - Reverting to the old value is better than clobbering to zero; if it can't change the field to