Ross Berteig wrote: >Did you actually try compiling with Makefile.mingw as is?
Tried it more than once. It fails without the lib location change on my system every time. >On Windows, the best way to check for errant DLL references is with DEPENDS. I typically use objdump to check what DLLs are referenced, but I believe our organization does have official copies of depends and other Microsoft products/toolsets if needed. Baruch Burstein wrote: >This is not the same miniz. By default fossil compiles and uses zlib. It is > distributed with the fossil source and does not use your system one. This > can of course be changed in the makefile. The miniz you are reffering to is > part of the zlib distribution. Saw that yesterday as I was reviewing the make process. So, I currently have it built and working with miniz rather than zlib (or libminizip). Will investigate getting it to build with the system zlib instead. Jan Nijtmans wrote: > However, I would recommend to use MinGW-w64, then you > can use all unicode characters in the command line you like A lot of die-hard original MinGW users including myself refuse to use MinGW-w64 due to licensing related issues. I feel everyone should be able to use the tools/utilities/compilers they're most comfortable with. I'm perfectly happy with my own MinGW fork and it does a few things that MinGW-w64 can't. Fossil definitely seems easier to build on Windows than many of the other version control alternatives out there. Thanks to everyone for the tips on building with MinGW. I'm still reading through the makefiles and source code. Once I'm sure I have the system libraries I want included in the build, I'll script the process so I don't have to do the build steps and makefile changes by hand. Sincerely, Laura _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
