Well, I do not like Frankenstein setups. I'd prefer to keep the Cygwin and AS Perl setups mutually exclusive.
I've copied the .pm files in the AS site/lib subdir and the .dll, .dll.a and .bs files in the site/lib/auto subdir.
When I execute my script in AS, I get an error message about a missing cygwin1.dll in my PATH.
I'm so close I can almost taste it... | [reply] |
Putting a copy of the cygwin dll into your AS perl bin directory would probably work.
Or if you don't wish to have 2 copies of the dll floating around, place the one copy somewhere it will be visible from both environments. Say, windows\system32 for example.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.
| [reply]
[d/l]
[select] |