"Kevin P. Lawton" wrote:
>
> "Jeffrey B. Siegal" wrote:
> >
> > "Kevin P. Lawton" wrote:
> > > The other issue that comes up, is how to ./configure the source
> > > so it can be compiled in Win32/MSVC++ land.
> >
> > People can run configure under Cygwin with the appropriate -- options
> > (specified in an INSTALL.W32 file). Or you can just deliver a
> > pre-./configure-ed makefile for Microsoft nmake. We do both for an open
> > source package we maintain which has to be portable to Windows.
>
> Yes, I like these options. Otherwise we have to duplicate the
> whole functionality of configure and the Makefile tree.
>
> This lets us standardize on configure. I do a similar thing
> with bochs. You have to configure on a supported platform,
> then use MS NMAKE.
>
> -Kevin
I think that configure is a fine option. I would assume that most
Windows users will be just that... USERS! I don't see a lot of people
actually attempting to build this stuff on Windows. Those who do can be
expected to have a fairly high level of expertise.
Kevin (or others), can you summarize the things that are going to be
required in the kernel mode driver? I'm especially interested in what
you think will end up being host-specific kernel functions. I'd like to
start at least thinking a bit about the necessary Windows kernel mode
driver stuff.
Craig
