This is the mail archive of the
mailing list for the Cygwin project.
Re: Inconsistence on file operation when the name already exists with exe extension
On 10/07/2012 17:24, Earnie Boyd wrote:
On Tue, Jul 10, 2012 at 4:34 AM, Aaron Schneider
You're right that cygwin shell tries to emulate bash, I just twisted things.
You're still wrong. Cygwin is a POSIX library for Windows. Bash is a
shell capable of being built with that POSIX library for use on
Windows but it isn't an emulation of Bash, it *is* Bash. Other shells
available on *nix is also available for Cygwin.
The problem is that in unix executables don't have extension but they actually do in cygwin so I think that's the root of the problem.
They don't need one in Cygwin either; as a matter of fact it was an
addition to binutils in the second generation of Cygwin that added the
.exe to the executable because it was more natural for Windows and
Windows at the time wouldn't execute the binary without the .exe
Probably compiling binaries under cygwin without the exe extension, like unix, is not an alternative, or is it? Cygwin may detect if it is executable checking if it's PE format; if it is perl script. Just check if file is present in path or run. /file
False. It is wholly possible, you just have to pass the correct flags
to the linker process. Current windows versions since at least XP and
maybe before would run files that did not contain a .exe extension.
I don't see how you can run a PE executable from windows shell (cmd.exe)
directly without the exe extension. I've just tried it in several ways
and always prompts me the "Open with..." dialog instead of directly
running it because treats it as data.
When you say that Windows XP and above can run an executable without
extension, you are talking about running it from windows shell. But I
was referring in the end to the cygwin terminal
(C:\cygwin\bin\mintty.exe -) that I believe can run exe without
extension even in older versions of windows, because it's bash that
launches it as you said before.
That's being said because I expect users to run commands from the cygwin
terminal. The exe extension is needed if you want to run the linux
commands directly from the windows shell directly (c:\cygwin\bin\ and
other bash PATHs should be exported to the windows PATH to run them
directly from windows shell, but you will mix things up)
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple