build after last update

John Ralls jralls at
Tue Jul 11 23:34:18 EDT 2017

> On Jul 11, 2017, at 3:07 PM, Geert Janssens <geert.gnucash at> wrote:
> On dinsdag 11 juli 2017 18:42:28 CEST Alex Aycinena wrote:
>> Geert,
>>> ---------- Forwarded message ----------
>>> From: Geert Janssens <geert.gnucash at>
>>> To: Alex Aycinena <alex.aycinena at>
>>> Cc: gnucash-devel <gnucash-devel at>
>>> 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 ?
>>> I didn't consider the latter when making my changes. Perhaps I should.
>>> Geert
>> No i didn't run ninja-build install but ran it from the build directory.
>> When John pointed out a short while ago that you could, I started doing so
>> because it saved a step and was faster.
>> Alex
> 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 
> restrictions it would work.
> But for sure my commits won't copy the images into the build directory where 
> they are searched. I'll see how to fix this.
> I must admit on my system 'ninja-build install' is hardly overhead. It takes 
> litterally 2 seconds on my ssd, so running from the build directory was not 
> something I considered important until now. I realize now not everybody has 
> the luxury of such performance.

Actually, I said that it ran from the build directory and then 20 minutes later said that it didn’t because the guile files were still splattered all over the build directory.

Rob changed that in the Distcheck implementation but I’ve been stuck in the mingw64 weeds and haven’t tested to see if running from builddir works.

John Ralls

More information about the gnucash-devel mailing list