On Sep 22, 2016, at 10:15 AM, jungle Boogie <jungleboog...@gmail.com> wrote: > > Do you have a few steps you can share on building fossil from source > on a Windows environment?
When I use Fossil on Windows, it’s always under Cygwin. I don’t bother with native binaries on Windows. If you’re on Windows 10, the “Bash on Windows” environment would also make this easier, as you could just say “sudo apt-get install fossil”. WSL was still pretty shaky last time I tried it, a few months ago, but none of the problems I recall should affect Fossil. Either way, those binaries should give you a much higher chance of bootstrapping a source build, as they’ve got bigger support organizations. (Red Hat + the Cygwin user base on the one hand, Canonical + Microsoft + the Ubuntu user base on the other.) My Windows development VMs all run Fossil built from source under Cygwin. I’ve never had a problem building Fossil that way. If you absolutely cannot use Cygwin, you may be able to use the Visual Studio Community tools. Microsoft development tools aren’t perfect, but within their limitations, they’re uncommonly solid. The last Windows fossil.exe build command I saw drh post was a Microsoft nmake command. Compare MinGW, which tries to have all the bleeding-edge GCC features pioneered on *ix platforms, but, lacking the same support base of Linux and such, MinGW frequently has breakages. I don’t have to use MinGW that often, but it seems like half the time I do have to use it, *something* has broken since the last time, and I have to work around it. They do fix things, but I’ve never found GCC on MinGW to have the same quality as GCC on any other mainstream *ix platform, including Cygwin. > cannot find -lmingwex So find libmingwex? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
