[GNC-dev] Missing package

John Ralls jralls at ceridwen.us
Wed Sep 25 20:21:38 EDT 2019

> On Sep 25, 2019, at 10:50 AM, Tommy Trussell <tommy.trussell at gmail.com> wrote:
> On Wed, Sep 25, 2019 at 12:00 PM Tommy Trussell <tommy.trussell at gmail.com>
> wrote:
>> Yes it seems likely that code that was new in July would not be in the
>> Disco repositories because they froze before April. So the trick is to make
>> the code available for building.
> You see, we have multiple realities to reconcile... Code that was created
> in July that needs to line up with code that froze in April.
> It occurs to me for my Bionic 18.04 goal it might be easier for me to
> tackle it by rolling back GnuCash to those versions that came out before
> Bionic froze in early 2018, and get those to build, and work on each "fails
> to build" problem one at a time, as they develop.


You're off on the wrong tack. Those are cmake tests to determine if certain functions are present and it's expected for some of them to fail. They cause preprocessor variables to be set or not and there are checks in the code that adjust what functions are called depending on those preprocessor variables.

There's seldom any need to look at CMakeOutput.txt or CMakeError.txt, and you need a good understanding of how build systems work first in order to interpret them. Just look at what cmake writes to the terminal, that almost always tells you what's wrong in simple terms.

John Ralls

More information about the gnucash-devel mailing list