You're going to have problems with the tarball right off. There's a file
called aux.c (IIRC) in the tarball. "AUX" (no matter the case) is
one of a handful of reserved file names in Windows.
You might try Services For Unix (which I just picked up for ~ $11 direct
from Microsoft)
as it augments the existing POSIX layer in Windows. SFU can actually deal
with files
that have reserved names. Cygwin can't because it sits on top of Win32.
Can you tell I've done this before? ;) Anyways, I got a little ways into it
before
I had to put it down (much like the Solaris port).
Mark: Are you going to give him a PMNS number for Windows? And while
you're handing
one out for that, how about defining one for Darwin (aka OS X)?
A 12" or 15" PowerBook with Airport Extreme would make a great PCP client ;)
-----Original Message-----
From: pcp-bounce@xxxxxxxxxxx [mailto:pcp-bounce@xxxxxxxxxxx]On Behalf Of
Mark Goodwin
Sent: Monday, December 15, 2003 9:37 PM
To: Andrej Kozlov
Cc: pcp@xxxxxxxxxxx
Subject: Re: Problem build pmcd and libpcp under Windows
On Mon, 15 Dec 2003, Andrej Kozlov wrote:
> I hoped, that I can compile pmcd and libpcp on Windows, and plugable pmda
> write self.
>
> I tried under cygwin. :-(
>
> Have anyone experience to build at least pmcd and libpcp unter Windows
> or under gygwin ?
AFAIK, nobody has tried this. You should be able to build most of
it under cygwin and package as a tarball. The pmcd, simple, trivial
and sample PMDAs should build too (probably not as DLLs, but should
work as daemons). If you get it going, please send in the patches
along whatever you end up with for the windows PMDA and the infrastructure
for adding a windows service for pmcd.
Thanks
-- Mark
|