Gisle Vanem wrote:

> I've built cherokee 0.4.25 on Windows (and MingW) with rather few
> patches.

  Ey, it's wonderful, great job! :-)

> As far I've tested it works fine. I built it with
> -DCHEROKEE_EMBEDDED=1 since I couldn't get the modules to work.

  Well, my expertise is not in Windows related stuff. I guess it might
  be something related to dlopen/dlsym, as far as I remember Windows
  uses LoadLibrary instead.

> But when I execute "cherokee -C ./cherokee.conf", the conf-file
> isn't read. How is it suppoosed to work? Hence the 'DocumentRoot'
> becomes the root of my disk (dangerous!) since a "lynx
> http://localhost/"; returns a dir-list (w/o icons) of my 'g:\'

  Yeah, the Windows support of the last release was - as I'm sure you
  have already seen - pretty basic: it was only compiling a few source
  files, besides the fact it needs some support to be added, for
  example, the grammar to read the configuration files was not ready
  for accepting DOS paths like "G:\".

  Anyway, it makes sense to me to work for sometime on making Cherokee
  work as a native Win32 application, supporting the same set of
  functionality as Cherokee on Unix, so if you agree we can use your
  current patches as the base of the full porting.

--
Greetings, alo.
http://www.alobbs.com
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee

Reply via email to