Mail Archives: cygwin/2006/04/23/11:01:12
On 23 April 2006 15:45, Oliver Vecernik wrote:
> Dave Korn schrieb:
>> Trying to mix win32 perl and cygwin is a recipe for tears. Sure, use
>> CPAN modules, that is of course a good idea; but if the *nix one doesn't
>> work under cygwin, fixing it or rolling your own or even just using the
>> bog-standard file i/o features in perl is definitely far safer.
>
> First of all: I was just missing the fact, that /dev/ttyS3 is there
> but did not show up in `ls /dev/ttyS3' as Igor stated. Thanks for the hint.
Thanks for confirming I understood you correctly!
> I'm still no perl expert and I have to learn "the correct way to do
> it". I want to write my modules as portable as possible and Cygwin
> seems to be the best approach. :-)
I absolutely agree, which is why I thought the advice to install activestate
perl was bad advice for your situation. Needlessly complex considering you
already have a perfectly good cygwin perl and needlessly less-portable
considering what you write in cygwin's perl can run on win32 and *nix whereas
win32 perl has lots of modules that won't run on *nix...
> I'm trying to get rid of using Visual Basic on Windows, which I used a
> lot in the past for such kind of things including using com ports. I
> installed Device::SerialPort altough some tests fail. I'm trying to
> find out why, but this may take some time and is probably not related
> with Cygwin anymore.
Are you doing bog-standard serial i/o to another device, or are you after
doing low-level metal-bashing bit-twiddling to the port signals directly? You
may need the ioperm package to enable the iopl/ioperm syscalls.
http://www.cygwin.com/ml/cygwin-announce/2003-02/msg00023.html
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -