# Embedded System with Yaws on Windows

Rudolph van Graan <>
Wed Feb 18 10:55:59 CET 2004

Hi Klacke,

> I don't understand why you are fiddling with the set_uid driver
> since it was removed from win32 build looong time ago.

My build insisted on using it... But read below, it was later fixed by
shifting to cygwin.

> What's worse in the de-cygwin procedure though are the
> Makefiles and the build scripts. On the other hand if you want
> to run yaws embedded inside your other win32/erl app, all you
> need to do is:

Our problem was that we didn't have a build procedure in Windows, other
than plain erlang and (obviously) nothing compiled directly. I have
subsequently installed a cygwin build environment and yes, everything
worked this way around. Actually, for me the *biggest* problem is that
I cannot get "target_system" to work in windows - hence we build on
linux (.tar.gz) and then convert it manually to windows. This is where
the de-cygwin approach started. If I could build everything (and maybe
I am just missing something obvious) from windows, I'd be happy to use
it.

On the topic... Do any of you have working code employed to start Yaws
from code? I.e. like in the exact syntax to use to configure everything
in "yaws.conf" in code?

The one thing I did note regarding yaws on windows was the fact that if
you want to specify "c:\web" as root-folder in yaws.conf, you have to
specify it as "/web"... This immediately raises the question of how to
specify "D:\web"..?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2112 bytes
Desc: not available
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20040218/8d63dc1e/attachment.bin>