This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Portable shell code between Cygwin and Linux
- From: Sven Köhler <sven dot koehler at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 08 Aug 2011 03:16:57 +0200
- Subject: Re: Portable shell code between Cygwin and Linux
- References: <80hb65b3ue.fsf@somewhere.org> <20110729201651.GB13084@calimero.vinschen.de> <1686210011.20110730161401@mtu-net.ru>
Am 30.07.2011 14:14, schrieb Andrey Repin:
> Greetings, Corinna Vinschen!
>
>>> For every shell code that I write, I'd like it to be portable both to Cygwin
>>> on Windows, and to Ubuntu Linux for example.
>>>
>>> It's kinda possible, but am blocked with such a use case:
>>>
>>> alias vpnup='exec sudo openvpn --config ~/config/client.vpn --writepid /tmp/openvpn.pid &'
>>>
>>> While this worked perfectly under Ubuntu, I've had to make up a customized
>>> version for Windows:
>>>
>>> alias vpnupwin='cd c:/home/sva/config; openvpn --config client.vpn --writepid c:/cygwin/tmp/openvpn.pid &'
>
>> Don't use Win32 paths. Use POSIX paths:
>
>> alias vpnupwin='cd /cygdrive/c/home/sva/config; openvpn --config client.vpn --writepid /cygdrive/c/cygwin/tmp/openvpn.pid &'
>
> Moreover, the very first line is wrong.
>
> Must be
>
> alias vpnup='exec sudo openvpn --config $HOME/config/client.vpn --writepid /tmp/openvpn.pid &'
>
> that's where his problem began, IMO.
I don't know, why you pointed that out. It's of no use to feed a path
like $HOME/something to a pure win32 binary.
(Certainly, this hint is kind of important for the ubuntu version of the
script, but not for the cygwin issue, which is solely because he's
mixing cygwin and win32 and expects it work without any complication)
--
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