On Tue, Apr 10, 2007 at 10:30:20AM -0400, Robert Pendell wrote:
>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
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
>>>
-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
On Mon, Apr 09, 2007 at 10:00:04PM +0100, Adye, TJ (Tim) wrote:
>Christopher Faylor wrote:
>>I don't see any reason to include a non-cygwin version of a program in
>>the *cygwin* distribution. If you don't have cygwin1.dll in the path,
>>then you aren't running in a cygwin environment.
>>
>>This i
Adye, TJ (Tim) wrote:
If that did what we wanted, then we wouldn't need the run package in the
first place. The run command hides the console for console applications
(or at least those that Windows thinks of as console applications) like
xterm. "cmd" gives you that pesky console.
Well, cgf sp
On 09 April 2007 22:07, Adye, TJ (Tim) wrote:
> Hi Dave,
>
> Dave Korn wrote on 09 April 2007 17:16:
>>
>>> You might have a better idea for where the non-Cygwin version
>>> should go - I just put it in /usr/bin/run-native.exe.
>>
>> Or just "alias run-native='cmd /c start '".
>
> If that di
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
> s
Hi Dave,
Dave Korn wrote on 09 April 2007 17:16:
>
> > You might have a better idea for where the non-Cygwin version
> > should go - I just put it in /usr/bin/run-native.exe.
>
> Or just "alias run-native='cmd /c start '".
If that did what we wanted, then we wouldn't need the run package in
"Adye, TJ (Tim)" wrote:
> Also, since the run package is now part of Cygwin (and doesn't seem to
> be maintained elsewhere), it seems an unnecessary confusion to maintain
> two branches. If you really don't like having anything not linked with
> cygwin1.dll as part of the distribution, then how ab
Hi Christopher,
Christopher Faylor wrote:
>
> I don't see any reason to include a non-cygwin version of a
> program in the *cygwin* distribution. If you don't have
> cygwin1.dll in the path, then you aren't running in a cygwin
> environment.
>
> This is not to say that I don't understand perf
On 09 April 2007 15:33, Adye, TJ (Tim) wrote:
> Hi Alexander,
>
> For many years I've continued to use Chuck Wilson's old run-1.1.4
> because it included a version that was linked without Cygwin
> (run-native.exe, built with VC). Although it doesn't have all the
> features of the Cygwin version (
On Mon, Apr 09, 2007 at 03:32:35PM +0100, Adye, TJ (Tim) wrote:
>For many years I've continued to use Chuck Wilson's old run-1.1.4
>because it included a version that was linked without Cygwin
>(run-native.exe, built with VC). Although it doesn't have all the
>features of the Cygwin version (eg. it
Hi Alexander,
For many years I've continued to use Chuck Wilson's old run-1.1.4
because it included a version that was linked without Cygwin
(run-native.exe, built with VC). Although it doesn't have all the
features of the Cygwin version (eg. it can't translate Cygwin mount
points), it does allow
13 matches
Mail list logo
