arm-elf-gcc problem

[bluebrother]

why aren't you guys just using the vmware image? It's linux and that behaves pretty similar to cygwin. As this image is available I personally don't see a reason to use cygwin for that anymore (except if you already have it up an running).

[Sentertainment]

why aren't you guys just using the vmware image? It's linux and that behaves pretty similar to cygwin. As this image is available I personally don't see a reason to use cygwin for that anymore (except if you already have it up an running).

I prefer running things natively

[bluebrother]

I prefer running things natively

cygwin is not native

[Llorean]

I'd say the whole argument between VMWare and Cygwin is this:

VMWare:
Pro: Easy Setup, Compiling takes ~half the time.
Con: Takes up a lot of disk space. Sometimes unreliable network access to the files.

Cygwin:
Pro: Smaller footprint on disk space. Easier to access your files.
Con: Setup can go wrong in a myriad of ways. Compiling is measured in decades rather than minutes.


Okay, so I'm exaggerating very slightly on that final point, but it's really Space and direct filesystem access vs Speed and ease of setup.

[Sentertainment]

I prefer running things natively

cygwin is not native

I thought only the command line was simulated...
It seems to be UNIX for DOS to me.

[GodEater]

I thought only the command line was simulated...
It seems to be UNIX for DOS to me.

Cygwin is a POSIX compatibility layer for Windows. This means that all the binaries that run in the cygwin environment get a lot of their API calls routed through the cygwin.dll which then has to translate them into windows calls. That's why it's not "native".