As I doubt anyone is actually building for Windows besides you, I would just make a Windows build. If it crops up in any other environments, then you can cut the new full release.
On Aug 20, 2017 1:22 PM, "Karl Kleinpaste" <k...@kleinpaste.org> wrote: > I need an opinion. > > I have found the problem where Windows upchucks during first-time user > module install, after refreshing crosswire. It's not a bug in the code. > It's that I have to invoke the compilers with -fno-delete-null-pointer-checks. > The code is fine, *IF* the @#$% compiler would stop arbitrarily > "optimizing" certain checks into oblivion. > > In principle, this bug should affect all builds, because both regular and > MinGW compilers on my Fedora boxes are 6.3.1, but experientially it seems > to have affected Windows builds only. Do I put out an entire new release, > 4.0.7, to be safe? Or just a Windows release, as e.g. 4.0.6a? > > Comments welcome. > > _______________________________________________ > xiphos-devel mailing list > xiphos-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/xiphos-devel > >
_______________________________________________ xiphos-devel mailing list xiphos-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/xiphos-devel