I have fixed the two issues I had and have updated my changes here... https://github.com/Bob-IT/gnucash-on-windows/tree/changes
If you want to try it before it is possibly uploaded then do the following... Grab setup-mingw64.ps1 from my changes branch and add a 'pause' statement between lines 392 and 393 Run the script and when you get to the pause, get the other files I have updated and replace the ones installed in 'gnucash-on-windows.git' Press enter to continue the script and when finished you should have a valid Msys2 build environment. Now just follow the rest of the instructions on building Gnucash and hopefully it will work. This environment is set up to work with 'webkitgtk3-2.4.11-999.51' version and when tested, reports could be opened along with charts. I did try the 'webkitgtk3-2.4.11-999.6' version which seemed to work in this environment but charts fail so maybe I have missed a dependency. There is one more version, 'webkitgtk3-2.4.11-999.7' but the file size is way bigger than previous versions so not sure if it is correct. Regards, Robert On Mon, 24 Mar 2025 at 10:32, Robert Fewell <14ubo...@gmail.com> wrote: > I have managed to get a build and install for a current version of the > Msys2 install but have two problems to fix. > > The first is "OpenSP" does not build, fails on the PO directory I think. > The second is that a patch for "bdw-gc" is not automatically being > applied, to get round this I have deliberately misspelt the file name in > gnucash.modules which allows me to drop to a shell and apply it manually > and then continue. > To get round the "OpenSP" build failure for testing I copied a working > "OpenSP" "src" and "build" directory when the build failed and then just > rerun the build phase. > > My changes are here, > https://github.com/Bob-IT/gnucash-on-windows/tree/changes > > For the "OpenSP" build failure, there must be an updated Msys2 > file/environment change but at the moment I can not see it, the following > is the failure. > > Making all in generic > make[2]: Entering directory > '/c/gcdev64/gnucash/stable/build/OpenSP-1.5.2/generic' > make[2]: Nothing to be done for 'all'. > make[2]: Leaving directory > '/c/gcdev64/gnucash/stable/build/OpenSP-1.5.2/generic' > Making all in po > make[2]: Entering directory > '/c/gcdev64/gnucash/stable/build/OpenSP-1.5.2/po' > make[2]: *** No rule to make target '/config.status', needed by > 'Makefile'. Stop. > make[2]: Leaving directory > '/c/gcdev64/gnucash/stable/build/OpenSP-1.5.2/po' > make[1]: *** [Makefile:544: all-recursive] Error 1 > make[1]: Leaving directory '/c/gcdev64/gnucash/stable/build/OpenSP-1.5.2' > make: *** [Makefile:428: all] Error 2 > *** Error during phase build of OpenSP: ########## Error running make -j > 13 *** [1/12] > > > For information, I tried doing the complete build on my September 2024 > Msys2 setup and it all worked and that was with an updated > gnucash-on-windows and jhbuild directory. > > Regards, > Robert > > > On Thu, 20 Mar 2025 at 21:41, flywire <flywi...@gmail.com> wrote: > >> https://www.gnucash.org/docs/v5/C/gnucash-guide/ch_python_bindings.html >> >>> Starting with GnuCash version 2.4 you can write Python scripts to >>> manipulate your financial data. >> >> >> >> Important >>> The Python extensions are an optional feature which creates additional >>> dependencies. To be able to use Python scripts, GnuCash must have been >>> built with the cmake -DWITH_PYTHON=ON … option enabled, otherwise all what >>> follows won’t work. At present this option is not enabled by default, so if >>> you need this, you may have to compile GnuCash from source yourself. But >>> some distributions offer it also as a separate package with a name like >>> python[version]-GnuCash >> >> There are GnuCash Windows users who want to use the Python bindings which >> hasn't really been possible since you removed them from the distribution. >> Most users just want access to the binaries and don't care how they are >> created though some (including myself) would like to build them if >> the process was reasonable. (A GitHub workflow would be terrific.) >> >> Regards >> >> On Wed, 19 Mar 2025 at 14:00, John Ralls <jra...@ceridwen.us> wrote: >> >>> Have you considered setting up a Linux build environment instead? You >>> can install your distro of choice in the Windows Subsystem for Linux (aka >>> WSL). Many of them have a package manager target similar to Debian/Ubuntu’s >>> `apt build-dep gnucash` that sets up everything you need except a code >>> editor. It’s much less frustrating than the MinGW64 environment. >>> >> _______________________________________________ >> 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
