(one of these days, I'll remember to hit Reply All first)
Alvaro Lopez Ortega wrote:
> Cherokee source tree includes a ripped off version of the pcre
> library.
But for some reason "configure" decided to link against my copy of PCRE
instead of the one included in the Cherokee source tree.
I've just tested Cherokee on my Win2k virtual machine (VMware Player is great
for testing code like this), and you're right - it wants pcre3.dll...
> Even if from the technical point of view it isn't the best
> approach, I think that it may be better if we use it rather than an
> external version of the library. Although it'd be enough to ship
> the DLL inside the installer.
> Philip, what do you think?
Based on the contents of config.log, configure picked up my external copy of
PCRE and linked against that instead of using Cherokee's internal copy of
PCRE. That seems a bit weird to me, and it's one of the reasons I never spent
much time learning how to use Autotools.
> No, the problem is that Windows doesn't have a fork() system call.
> I guess we will have to wait to get Cherokee running as a service
> rather than as an common application.
Something else I need to read up on, I guess... Last time I checked, writing
services wasn't too hard (it's mostly a case of adding a couple of API calls
to register a task as a service process), but services will only run on
NT-class systems - Win2000 and WinXP.
It is a 'cleaner' way to do it, though - no perpetually minimised console
windows to ignore :)
--
Phil. | Kitsune: Acorn RiscPC SA202 64M+6G ViewFinder
[EMAIL PROTECTED] | Cheetah: Athlon64 3200+ A8VDeluxeV2 512M+100G
http://www.philpem.me.uk/ | Tiger: Toshiba SatPro4600 Celeron700 256M+40G
_______________________________________________
Cherokee mailing list
[email protected]
http://www.0x50.org/cgi-bin/mailman/listinfo/cherokee
