Re: Building unstable on Mac

Huzzah. File bug reports, setting the version to 2.7.x--after searching first, of course. Profiling and memory-checking are best done with Instruments, included with Xcode. Regards, John Ralls > On Feb 22, 2018, at 9:10 AM, R. Victor Klassen wrote: > > Success > > I

Re: Building unstable on Mac

Success. I have a running copy of unstable. That it took this long is at least in part because I’ve only had part time to attend to it. Also, for the first few weeks I didn’t realize that when my display was going to sleep, the entire build process was stopping, so nothing was happening

Re: Building unstable on Mac

Oops, that’s set in my personal (and a bit complex for building a variety of project) .jhbuildrc-custom. The moduleset should use $JHBUIILD_SOURCE. To work around it, add os.environ[‘SRCROOT’] = checkoutroot somewhere in .jhbuildrc-custom. Regards, John Ralls > On Feb 21, 2018, at 2:10 PM,

Re: Building unstable on Mac

Getting real close. CMake Error at common/cmake_modules/GncAddTest.cmake:145 (MESSAGE): GTEST not found. Please install it or set GTEST_ROOT or GMOCK_ROOT Call Stack (most recent call first): CMakeLists.txt:593 (GNC_GTEST_CONFIGURE) -- Configuring incomplete, errors occurred! See also

Re: Building unstable on Mac

Do you not know your way around autotools? Maybe it's time for a little RTFM [1] or you might prefer WTFV [2] (Watch the Fine Video). Anyway, configure writes a detailed log file called config.log. You'll usually find useful details about configuration errors and anomalies in there. It's

Re: Building unstable on Mac

> On Feb 1, 2018, at 6:31 PM, John Ralls wrote: > > > Please remember to copy the list on all replies. Not intentional. > > Well, if it was installed then why isn't libsoup finding it? I guess that’s what I’m asking. Thoughts on where to look for the answer? > >

Re: Building unstable on Mac

Please remember to copy the list on all replies. Well, if it was installed then why isn't libsoup finding it? Regards, John Ralls > On Feb 1, 2018, at 2:50 PM, R. Victor Klassen wrote: > > … or what happened that it wasn’t found? > > I scrolled back (actually used find)

Re: Building unstable on Mac

Yes, "refusing to switch a dirty tree" comes from xmlsec because it has configuration products committed into its repo. You can actually just 2 -- ignore and continue to configure. The boost line should be "for i in `ls $PREFIX\lib\libboost*.dylib`..." just like the one underneath it. I

Re: Building unstable on Mac

At some point I got the “refusing to switch to a dirty tree” error. I followed the instructions at https://lists.gnucash.org/pipermail/gnucash-devel/2015-March/038616.html [git reset --hard HEAD] Hope that’s OK. Next

Re: Building unstable on Mac

You didn’t build gtk-doc and Pango requires at least the macros for it. As to your question, it depends. It’s telling you on the line just below your question that pango is the seventeenth out of sixty-five packages, but it doesn’t know that some of them build in a couple of seconds and others

Re: Building unstable on Mac

Broke in pango - errors below: [Is there a file or other accessible reference that I can look into to get some idea of what fraction of the way through I am?] *** Configuring pango *** [17/65] autoreconf -fi acinclude.m4:68: warning: the serial number must appear before any macro definition

Re: Building unstable on Mac

Op dinsdag 30 januari 2018 17:50:01 CET schreef Aaron W. Swenson: > On 2018-01-29 20:02, John Ralls wrote: > > To build unstable: > > … > > 7. make && make install > > > > To run tests, run > > > > make check > > Are these really correct? I thought all of that got stripped out. Those are

Re: Building unstable on Mac

On 2018-01-29 20:02, John Ralls wrote: > To build unstable: > … > 7. make && make install > > To run tests, run > make check Are these really correct? I thought all of that got stripped out. signature.asc Description: Digital signature ___

Re: Building unstable on Mac

To build unstable: 1. Retrieve the latest .jhbuildrc-custom from the gnucash-on-osx repository. 2. Edit ~/.jhbuildrc-custom to comment out the gnucash-stable prefix and modules and to uncomment the gnucash-unstable ones. 3. Run jhbuild bootstrap 4. Run jhbuild build If you want a git checkout,

Building unstable on Mac

So, the wiki is less than clear on how to do this. First I tried going through the instructions under Building for Development beginning with jhbuild shell cd $PREFIX/../src/gnucash-2.6.17 But it turned out that there was no path with the prefix $PREFIX/../src No src directory had yet been