R
Ric Thompson
Guest
I've had this problem on a couple of projects now, but I'm not sure
what the best fix is.
I have an environment which is set up for Unix, with scripts and
makefiles containing mainly relative paths, but with some paths rooted
at '/'. I also need to get these projects working on Windows/cygwin.
On cygwin, the bash scripts and makefiles run Ok, and cygwin makes
sure that paths rooted at '/' actually appear at 'c:\cygwin\' in the
file system. However, if I have a script which includes the command
'vcom /myfile' then vcom/vsim attempt to open 'c:/myfile', and not
'c:/cygwin/myfile'. They presumably bypass the cygwin API in some way.
Any ideas on the best way to handle this? Ideally, I want to use
exactly the same scripts and makefiles on Unix and Windows.
Cheers
Ric
what the best fix is.
I have an environment which is set up for Unix, with scripts and
makefiles containing mainly relative paths, but with some paths rooted
at '/'. I also need to get these projects working on Windows/cygwin.
On cygwin, the bash scripts and makefiles run Ok, and cygwin makes
sure that paths rooted at '/' actually appear at 'c:\cygwin\' in the
file system. However, if I have a script which includes the command
'vcom /myfile' then vcom/vsim attempt to open 'c:/myfile', and not
'c:/cygwin/myfile'. They presumably bypass the cygwin API in some way.
Any ideas on the best way to handle this? Ideally, I want to use
exactly the same scripts and makefiles on Unix and Windows.
Cheers
Ric