OK. Regards, John Ralls
> On 31 Mar 2025, at 05:17, <russ.go...@gmail.com> <russ.go...@gmail.com> wrote: > > I do have some experience with Cmake. We had a fairly mature cmake system > that I helped maintain and develop which built our code base for Linux and > Windows (both native compilers) but it's been 2 years since I've done any > development so everything is some relearning of course. > > -----Original Message----- > From: John Ralls <jra...@ceridwen.us> > Sent: Sunday, March 30, 2025 11:07 AM > To: russ.go...@gmail.com > Cc: gnucash-devel <gnucash-devel@gnucash.org> > Subject: Re: CMake technical debt > > Not for me. Build system problems are a major pain point so they tend to get > attended to. > > That doesn’t mean there aren’t things that could be done better. Do you have > a lot of experience with cmake? > > Regards, > John Ralls > > >> On Mar 30, 2025, at 8:33 AM, <russ.go...@gmail.com> <russ.go...@gmail.com> >> wrote: >> >> I’m now building successfully all the opaque pieces on windows, and it seems >> to install and run. >> I was wanting to get more familiar with the anatomy/topology of the code >> base. >> I was thinking of doing something in the CMake realm to gain some >> familiarity there. >> Is there anything that is annoying the developers that would be beneficial >> to fix/change in CMake realm but is not critical path for anything? >> Thanks. >> _______________________________________________ >> gnucash-devel mailing list >> gnucash-devel@gnucash.org >> https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel