Re: How to identify compilers

"Robert" <robert.kahlert@aeg-hausgeraete.de> wrote in message
> Did anybody know, if (and how) it's possible to find out with which
> compiler a Windows executable file was compiled.


Everyone's mentioned the right way to go about finding this out in
general.


For quick-and-dirty answers, the simple way is to run a dependency
checker such as Dependency Walker (he author, Steve Miller, is a
fairly well known former Microsoft dev - he produced the tool while
there, and keeps a current version of it up at stevemiller.net).


Without being exhaustive, here's what you can tell:


+ If it can't open, it's probably a 16-bit app.


+ It will have explicit dependencies on DLLs - some standard system
files, others very obviously application runtimes. Dependency on
msvbvm60, msvbvm50, or vb40032 DLL will clue you in that it is a VB
app. explicit direct dependency on a common FORTRAN runtime will tell
you its a Fortran app. _Lack_ of the above, combined with a _direct_
msvc* file dependency, will clue you in that it's a C++ app.


Do that a few times, and then you can open an arbitrary binary in a
hex editor, scan a few lines, and come up with a good guess for its
compilation environment.

Return to the comp.compilers page.
Search the comp.compilers archives again.