On 11/12/19 7:56 PM, John Ralls wrote: > > No. Anything involving make, ninja, cmake, gcc, clang, guild, etc. is a build > operation and should happen in a build directory. So after getting the clone > to the commit you want and assuming that the clone is in a directory named > gnucash.git: > > mkdir ../gnucash-build && cd ../gnucash-build > cmake -DWHATEVER_OPTIONS ../gnucash.git > make dist > > Regards, > John Ralls > Thanks John. I discovered that make dist didn't work in the git repository. Tried the cmake/make route but that threw errors. Rebooted and read your email. Tried again and it worked.
However, comparing the tar.gz from Sourceforge and the one created by the above starts off with this difference (and proceeds for pages). I suspect something on my machine must be newer than when the sourceforge distribution was created. I'm too tired to figure out the next steps but I'm aiming to see if I can get sbuild to work on the tar.gz files. Thanks for being patient with me. And maybe I'm overthinking my new setup: Details only for those who might be interested: in my $HOME/Projects/GnuCash folder (which holds other items like my formatted balance sheet scm code): mkdir gnucash-git mkdir gnucash-build mkdir gnucash-build/v3.7 cd gnucash-git git clone https://github.com/Gnucash/gnucash.git maint git checkout maint git worktree add ../v3.7 3.7 cd ../../gnucash-build/v3.7 cmake --WITH_PYTHON=ON -DCMAKE_BUILD_TYPE=Release ../../gnucash-git/v3.7 make dist _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
