On 01/01/2010 07:06 AM, neil.mowb...@calgacus.com wrote:
I suppose at its core the question is about the intent of cygwin. Is
it (1) to provide unix like capabilities to a MS platform (in which case
one would expect/demand a high degree of interoperability), or
(2) to provide a unix like isla
neil.mowb...@calgacus.com wrote:
For the most part the cygwin tools interoperate with MS artifacts but
it does break down, especially, with 64bit artifacts. For example, nm
can work with 32bit object files created by MS cl.exe but it cannot
work with 64bit MS object files (unrecognised file for
On 1/1/2010 20:37, JonY wrote:
On 1/1/2010 20:06, neil.mowb...@calgacus.com wrote:
Folks,
A bit of a vague question but any greater clarity concerning the
appropriate
level of interoperability between Cygwin and MS would be appreciated.
I have my Windows 6 and 7 platforms configured to build s
On 1/1/2010 20:06, neil.mowb...@calgacus.com wrote:
Folks,
A bit of a vague question but any greater clarity concerning the appropriate
level of interoperability between Cygwin and MS would be appreciated.
I have my Windows 6 and 7 platforms configured to build software using
different toolchai
Folks,
A bit of a vague question but any greater clarity concerning the appropriate
level of interoperability between Cygwin and MS would be appreciated.
I have my Windows 6 and 7 platforms configured to build software using
different toolchains, the most common being (1) Visual Studio 10 and (2)
5 matches
Mail list logo
