You could create a Windows symbolic link using the Windows 'mklink'
tool though, and it should work both in cmd.exe and in Cygwin.
Thanks for the info and Corinna's quote.
Probably I'll just create windows symlinks like from
c:\users\tuli\bin\gcc.exe to c:\cygwin\bin\gcc-3.exe
so that cygwin
On 01/01/2010 04:52 PM, Lee Rothstein wrote:
Will Windows junctions (for the path; plus the file name) work, here, Andy?
(http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)
NTFS junctions are for directories only.. For files and directories, one could
use mklink on Vista and
Will Windows junctions (for the path; plus the file name) work, here, Andy?
(http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)
(Admittedly, a kludge, but this is Windows, after all. ;-))
Lee
Actually, in Windows 7, Microsoft has implemented true symbolic links
(as far as I
Lee Rothstein:
Will Windows junctions (for the path; plus the file name) work, here?
Don't think so, afaik junction points (introduced in Win2000, and
different from Vista/7 symlinks) work correctly for directories only.
Hard links, however, should work just fine for the problem at hand.
tuli
This is a known limitation of the symbolic links in Cygwin 1.7. The solution
is ...
Thanks for the info. I'll try one of your workarounds.
Cheers,
Tuli
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
2009/12/30 Larry Hall (Cygwin):
I've been using gcc and other tools in older versions of cygwin with
32-bit Windows XP and Vista from windows command prompt (cmd.exe)
without problems. But now I'm using 64-bit Windows 7, and some command
line tools like gcc.exe do not work anymore (from
On 12/30/2009 08:30 AM, tuli tanssi wrote:
Hi,
I've been using gcc and other tools in older versions of cygwin with
32-bit Windows XP and Vista from windows command prompt (cmd.exe)
without problems. But now I'm using 64-bit Windows 7, and some command
line tools like gcc.exe do not work
7 matches
Mail list logo
