I managed a successful build of fossil on Windows, through the kind help of other list members.
The only outstanding issue is some undefined references when FOSSIL_ENABLE_SSL=1: ../../GnuWin32/lib/libcrypto.a(rand_win.o):rand_win.c:(.text+0xa3a): undefined reference to `_getdevicec...@8 # more GDI32 unresolved externals ../../GnuWin32/lib/libssl.a(ssl_cert.o):ssl_cert.c:(.text+0x76d): undefined reference to `_X509_STORE_CTX_init' # more internal openssl unresolved externals I would have thought the first class of unresolved could be sorted by modifying Makefile.w32 so it holds: LIB = -lmingwex -lz -lws2_32 -lgdi32 But it doesn't seem gdi32 holds the GDI functions the linker is looking for. Anyone else seeing this problem when building with SSL on Windows? Thanks for any help and advice you can provide, Bjorn On 29 March 2010 22:22, Ross Berteig <[email protected]> wrote: > At 04:05 AM 3/29/2010, Bjorn Toft Madsen wrote: > >Be that as it may, is there anybody on this list who has > successfully > >built fossil w/ssl on Windows? > > Not with SSL as yet, but I could try it. > > >Taking a binary off you (the hypothetical Win builder) or not, I'd > >love to pick your brain on your environment so I can build > myself. My > >Windows awk doesn't do what I think the makefile expects it to > do and > >I've got other errors that make me believe the standard DOS shell > >isn't enough to build my own binary. > > I have both MingW and MSYS installed, along with the GnuWin32 > build of Gnu make. (Not to mention a lot of the rest of the > GnuWin32 packages, but I don't think they enter into this > question, aside from zlib.) > > I cloned the repository from fossil-scm.org in the usual way, > then opened it into a working folder. I created a sub-folder for > my windows build, an in there I created a config.w32 file > containing two customizations for my environment: > > SRCDIR = ../src > TCC += -I/e/Programs/GnuWin32/include -L/e/Programs/GnuWin32/lib > > The SRCDIR is required to point to the actual fossil source tree, > since I'm building in a separate folder. The second is required > to add references for the include and library files for zlib as > distributed by GnuWin32. I'd guess that if I were to configure > SSL, I'd use the GnuWin32 build of the library, and that this > setting would cover that as well. Note that I was careful to > install all GnuWin32 packages into a folder with no spaces > anywhere in its full name. That makes it a lot easier to deal > with for this kind of thing. That folder happens to be on E: due > to a quirk of my XP install that resulted in there being no drive > C:, but your mileage almost certainly will differ. > > From MSYS bash (running in a normal console window, not rxvt) I > change the current directory into my windows build folder, then > use make -f ../Makefile.w32 to build. Once I located the zlib > package, it built on the first try. > > Even with all of the GnuWin32 core *nix utilities installed, I > wouldn't expect the makefile to do the right thing with CMD.EXE > as the shell, especially with its use of awk to write VERSION.h > from the manifest of the current checkin which suffers badly from > the difficulty of correctly quoting command line arguments in > CMD.EXE. It is remotely possible that you can teach make to use > MSYS bash as its shell, but then you'd have to get the paths > translated correctly. All in all, it is much easier to just use > the MSYS environment for building. > > > Ross Berteig [email protected] > Cheshire Engineering Corp. http://www.CheshireEng.com/ > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
