Mail Archives: cygwin/2006/07/28/10:32:14
%% "John W. Eaton" <jwe AT bevo DOT che DOT wisc DOT edu> writes:
jwe> On 28-Jul-2006, Paul D. Smith wrote:
| Regardless, I still wonder whether my idea of building make for a POSIX
| environment with Cygwin, but setting HAVE_DOS_PATHS explicitly, would
| work.
jwe> If this could cause some valid Makefiles to do the wrong thing as
jwe> cgf suggests might happen,
Hm. I don't think I saw that message?
Certainly there are obscure cases where enabling DOS path support will
behave differently, but they're pretty rare I believe. Is this a Cygwin
thing?
jwe> then can we at least make the behavior optional, perhaps with a
jwe> command line option or magic target (maybe
jwe> ".WINDOWS_FILENAMES:")?
This would be very tricky: right now all the code to do DOS vs. POSIX
pathnames is controlled through #ifdefs, so it's a compile-time thing.
Changing it to a runtime thing would be a lot of work, I think... the
#ifdeffing in GNU make is kind of a mess, with all the different ports
we support.
Honestly, I don't see a lot of benefit to it. On a Windows system, even
in Cygwin, I would assume that everyone would always expect anything
that looked like a Windows pathname to be treated like a Windows
pathname. We're not talking about enabling this support on UNIX, just
in Cygwin.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith AT gnu DOT org> Find some GNU make tips at:
http://www.gnu.org http://make.paulandlesley.org
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -