Re: Pathproblems while using CygWin as development environement on Win

Hi LanX,

It's been a really long time since I last used CygWin, but I am curious if you've tried using File::Spec or Path::Class for portability? Also, can you use relative pathnames instead of absolute, or at least anchor absolute paths to some common place, such as the script's path (FindBin)?

Regards,
-- Hauke D

Comment on Re: Pathproblems while using CygWin as development environement on Win

Replies are listed 'Best First'.
Re^2: Pathproblems while using CygWin as development environement on Win by LanX (Saint) on Nov 11, 2016 at 11:36 UTC
If I understand you correctly you are suggesting to change the Perl code. But I don't have a portability issue, the code is never supposed to run under cygwin or Unix Perl. I (probably) need something on the level of Perlrun to force Perl emitting relative paths. There are many possibilities, I'm looking for the simplest and most robust. Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]
Re^3: Pathproblems while using CygWin as development environement on Win by haukex (Archbishop) on Nov 11, 2016 at 12:15 UTC
Hi LanX, Ok, I get what you are asking now, and in that case my suggestions - at least in regards to changing the scripts themselves - don't apply. Perhaps what you want to do can be solved with some kind of wrapper script, but since I don't have cygwin around at the moment I don't have any ideas, sorry... Regards, -- Hauke D	[reply]
Re^4: Pathproblems while using CygWin as development environement on Win by LanX (Saint) on Nov 11, 2016 at 12:21 UTC
> since I don't have cygwin around at the moment I don't have any ideas, sorry... Please, no worries! Many others praise cygwin here, so I thought they might have already solved this. Thanks for your help! :) Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]