On Thu, Jun 14, 2007 at 09:09:17AM -0700, Justin Bailey wrote: > On 6/14/07, David Roundy <[EMAIL PROTECTED]> wrote: > >Why replace three more powerful options with a single less powerful option > >that also complicates the build process (not the configure script, but the > >sequence that user must go through to compile darcs)? I do hope that at a > >minimum the new patch allows us to compile without HTTP support? > > I think the build process is less complex with this library. In order > to create the patch, I needed to build darcs on Windows. It was > definitely a non-trivial process (see these instructions on the wiki: > http://darcs.net/DarcsWiki/BuildingUnderWindows). Libcurl was a small > but fragile portion of it. I needed to download a library, ensure it > was built correctly itself, and then, because my MinGW installation > had some strange paths, I needed to be sure to pass the right compiler > flags to configure (CPPFLAGS & LDFLAGS). At least with the HTTP > library, the download and install is pretty straightforward due to > Cabal packagin, and no extra flags are required.
Compiling anything on windows is a pain, but you didn't need to install libcurl. Without libcurl, darcs works fine as long as either curl or wget is in your path. Unless for some reason the curl/wget support is broken on windows? -- David Roundy Department of Physics Oregon State University _______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
