On 10 April 2007 15:30, Robert Pendell wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Adye, TJ (Tim) wrote:
>> Brian Dessent wrote on 09 April 2007 22:05:
>>> If you really want a compromise solution, you could modify
>>> run to not depend on cygwin1.dll at link-time but instead
>>> LoadLibrary() it at runtime, and if that fails fall back to
>>> whatever the native version would have done. Thus you get a
>> That's a nice idea, but I suspect it would indeed cause more confusion
>> than any gain - especially when we're only talking about a 50k
>> executable. Imagine the program silently behaving differently if you
>> change the PATH. A nice "cygwin1.dll was not found" error message is
>> usually preferable :-)
>>
>> I hope that a separately-named (small) executable, perhaps installed
>> elsewhere, will be acceptable.
> I actually agree with cgf on this one but just an idea here. If that
> kind of function was implemented then a warning could be placed to say
> something to the effect of...
>
> WARNING: cygwin1.dll was not found in the path. Using native windows
> paths instead.
Or just "alias run-native='cmd /c start /b '".
Seriously, without unix-style path conversion, what else of any substance is
left for run-native to actually *do*? I'm convinced this whole idea is the
wrong over-engineered solution to an elementary non-problem. An alias or
script is a far better fit to the requirements.
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/
