%% Stephen Huntley <[EMAIL PROTECTED]> writes:

  sh> 1.  Forward slashes on Windows.

  sh> I like that gnu make has so many cross-platform capabilities, but
  sh> the fact that on Windows the automatic variables always deliver
  sh> pathnames with backslashes even when using sh.exe is a major pain.
  sh> My rules are littered with expressions like $(subst \,/,$<).  I'd
  sh> like an option that causes automatic variables to deliver forward
  sh> slashes on Windows if sh.exe is being used as the shell.

To the best of my knowledge (which is not that great for Windows), make
simply provides file names as strings.  It certainly doesn't do any
slash manipulation.

In other words, if you write your filenames using forward slashes your
auto variables will contain forward slashes.

You might want to try the [EMAIL PROTECTED] mailing list for
Windows-specific issues with GNU make.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <[EMAIL PROTECTED]>          Find some GNU make tips at:
 http://www.gnu.org                      http://www.paulandlesley.org/gmake/
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist

_______________________________________________
Help-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/help-make

Reply via email to