-----Original Message-----
From: Ulrich.Herbst
3. I don't want to build Win32::Eventlog on my own... for these reasons:
- I had to do it on many systems...
- We don't have compilers and make and tools... installed on them
(production environments)
Ok - alternatively it's only *2* files that need to be installed -
Win32/EventLog.pm and auto/Win32/EventLog/EventLog.dll.
After you've manually built the module on your local machine, you'll find
the former in blib/lib and the latter in blib/arch.
Assuming you're running the same version of perl across all systems, it's
just a matter of installing those files into one of the @INC directories on
all machines.
By convention, I think you'd install them into
/usr/lib/perl5/site_perl/5.14 - so you'd end up with
/usr/lib/perl5/site_perl/5.14/Win32/EventLog.pm
and
/usr/lib/perl5/site_perl/5.14/auto/Win32/EventLog/EventLog.dll
If it's simple for you to effect that across the various systems, then you
could go with that.
So - will be in the near future a libwin32-version including
Win32::Eventlog running with Perl5.14 available from cygwin installer ?
I'm sort of thinking it should already be there. I'm running perl-5.14.2 on
Cygwin-1.7.17, so I figured I'd test for myself ... alas, I can't find a
mirror that can provide setup.ini, and setup.exe aborts at that point.
So I guess we wait for someone who *knows* to come along.
Btw, it would really help if, in your testing, you'd try to load
Win32::EventLog instead of Win32::Eventlog. In some situations it probably
doesn't matter, but testing the loading of "Win32::Eventlog" introduces an
(unnecessary) uncertainty with which it would be better to go without.
The thing is that, although Windows is not case-sensitive, perl is - and
failing to attend to case-sensitivity can lead to strange failures.
Cheers,
Rob
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple