On woensdag 12 juli 2017 05:34:18 CEST John Ralls wrote:
> > On Jul 11, 2017, at 3:07 PM, Geert Janssens
> > wrote:>
> > Hmm,
> >
> > I had my doubts about it at the time John suggested one could run from the
> > build directory, but didn't have time then to question/test further under
> > what
gnucash-devel
>>> Bcc:
>>> Date: Mon, 10 Jul 2017 23:01:22 +0200
>>> Subject: Re: build after last update
>>> Alex,
>>>
>>> I wonder did you run ninja-build install or are you running gnucash from
>>> the
>>> build directory
On dinsdag 11 juli 2017 18:42:28 CEST Alex Aycinena wrote:
> Geert,
>
> > -- Forwarded message --
> > From: Geert Janssens
> > To: Alex Aycinena
> > Cc: gnucash-devel
> > Bcc:
> > Date: Mon, 10 Jul 2017 23:01:22 +0200
> &g
Geert,
> -- Forwarded message --
> From: Geert Janssens
> To: Alex Aycinena
> Cc: gnucash-devel
> Bcc:
> Date: Mon, 10 Jul 2017 23:01:22 +0200
> Subject: Re: build after last update
> Alex,
>
> I wonder did you run ninja-build install or are
--
> > From: Geert Janssens
> > To: Alex Aycinena
> > Cc: gnucash-devel , John Ralls <
> > jra...@ceridwen.us>
> > Bcc:
> > Date: Mon, 10 Jul 2017 12:28:09 +0200
> > Subject: Re: build after last update
> >
> > On zondag 9 juli 2017 22:33:3
> -- Forwarded message --
> From: Geert Janssens
> To: Alex Aycinena
> Cc: gnucash-devel , John Ralls <
> jra...@ceridwen.us>
> Bcc:
> Date: Mon, 10 Jul 2017 12:28:09 +0200
> Subject: Re: build after last update
> On zondag 9 juli 2017 22:33:34 CE
On zondag 9 juli 2017 22:33:34 CEST Alex Aycinena wrote:
> Spoke too soon. When I tried to start gnucash with 'bin/gnucash --debug
> --log gnc.scm=debug --nofile', got:
>
> gnc.gui:ERROR:/home/gnucash-dev/gitcheckouts/gnucash-clean-new/src/gnome-uti
> ls/gnc-icons.c:103:gnc_load_app_icons: asserti
On Sun, Jul 9, 2017 at 1:28 PM, Alex Aycinena
wrote:
>
>
> On Sun, Jul 9, 2017 at 8:31 AM, Alex Aycinena
> wrote:
>
>>
>>
>> On Sun, Jul 9, 2017 at 3:51 AM, Geert Janssens <
>> geert.gnuc...@kobaltwit.be> wrote:
>>
>>> I had the same issue here and I've just pushed a fix.
>>>
>>> It turns out ou
On Sun, Jul 9, 2017 at 8:31 AM, Alex Aycinena
wrote:
>
>
> On Sun, Jul 9, 2017 at 3:51 AM, Geert Janssens > wrote:
>
>> I had the same issue here and I've just pushed a fix.
>>
>> It turns out our cmake config files use a different check for packages
>> based
>> on the version of cmake itself. I
On Sun, Jul 9, 2017 at 3:51 AM, Geert Janssens
wrote:
> I had the same issue here and I've just pushed a fix.
>
> It turns out our cmake config files use a different check for packages
> based
> on the version of cmake itself. I presume there was a bug in cmake 3.1-3.4
> that made this necessary.
I had the same issue here and I've just pushed a fix.
It turns out our cmake config files use a different check for packages based
on the version of cmake itself. I presume there was a bug in cmake 3.1-3.4
that made this necessary.
The default cmake fails on the "OPTIONAL" modifier. where the c
> On Jul 8, 2017, at 5:38 PM, Alex Aycinena wrote:
>
> After the last update, my Fedora 25 system won't build with the following
> output:
>
> [gnucash-dev@HPdv5Fedora gnucash-working-build]$ make
> -- Checking for modules 'OPTIONAL;webkit2gtk-4.0'
> -- No package 'OPTIONAL' found
> -- No
After the last update, my Fedora 25 system won't build with the following
output:
[gnucash-dev@HPdv5Fedora gnucash-working-build]$ make
-- Checking for modules 'OPTIONAL;webkit2gtk-4.0'
-- No package 'OPTIONAL' found
-- No package 'webkit2gtk-4.0' found
-- Checking for module 'webkit2gtk-3.0'
13 matches
Mail list logo