building windows build ([Bug 641832] Crash opening MySQL database after installing 2.4.2 over 2.4.0)

[Christian Stimming]

Am Sonntag, 13. Februar 2011 schrieb John Ralls:
> BTW, the windows build is absolutely hideous for developing in. `make &&
> make install` doesn't, which is why I thought yesterday that I hadn't
> correctly diagnosed the problem when I had. Instead, one has to run
> make_install.sh, which grinds through a complete autoconf.sh && configure
> cycle, and because that touches config.h, *everything* has to rebuild,
> which takes about 45 minutes

I know, I know. However, the gnucash build requires the PATH to contain some 
of the bin/ directories which have been created before by install.sh. If your 
install.sh runs until the end, it displays a nice long message about all the 
"export ..." variables that you should add to your msys' /etc/profile. I did 
that on my windows build computer so that PATH contains autotools/bin, 
gnome/bin, and so on, and because of that "make; make install" indeed does 
work there. If it doesn't at your computer, it's because your msys' PATH 
doesn't contain some entries, but once you add them there, all is fine.

> Can't we move whatever
> special sauce is in the shell scripts into Makefile.am so that it will
> work?

All special sauce is there, except for the PATH, which you must modify 
yourself.

> Also, make check fails in the second check because of a problem with
> future_modules. Obviously, more special sauce is needed in the test code,
> because Gnucash itself has no problem loading modules.

Hm... I never tried "make check" on windows, because it would require to set a 
new PATH in each test sub-directory because different from linux, the (test) 
executables don't know the locations of the newly compiled libraries (through 
the ELF rpath), so we would have to fix PATH each time per hand. I quickly 
gave up on that one at the time, and haven't ever touched that again.

Regards,

Christian