[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dependencies: non-standard path to system headers

From: Brian Dessent
Subject: Re: Dependencies: non-standard path to system headers
Date: Tue, 01 Jul 2008 10:11:45 -0700

Ineiev wrote:

> WinAVR gcc produces dependencies that shall confuse `make',
> like these:

The essential point is that using native Win32 tools with Cygwin causes
problems.  This is because Cygwin is designed to closely emulate a POSIX
environment, and the tools aren't equipped to deal with Win32 paths with
drive letters.  This is not specific to 'make', it is a general fact of
life with Cygwin.  Since the codepaths of Cygwin ports of these tools
are the same as the *nix codepaths, there is no guarantee that drive
letters will work.

Now, in the specific case of GNU make there is a patch in upstream make
to enable the handling of Win32 style paths even when built in unix
mode.  So you should just use a more recent 'make' from CVS and it
should just work.

But again I must emphasize that the core philosophy of Cygwin is to be
able to build *nix tools for Windows without source modification, or
with very minimal modification.  You shouldn't be surprised then that
these tools don't cope with Win32 paths because they wouldn't cope with
drive letters when built under linux either, and it's the same
codepath.  In other words, Cygwin exists specfically so that things like
dealing with Win32 paths need NOT be added to the code -- the tools
don't need to be "ported to Win32" they just need to be recompiled. 
This is far from the only example where you will encounter this clash if
you continue to mix native apps with Cygwin tools.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]