Make processor build and run on win32

[GoogleCodeExporter]

I need to move between computers a lot to test the various Airbag
components.  It would be convenient for me if the airbag processor library
and tools could be built as native win32 using the MSVC toolchain.

Attached is a rough first patch that builds a usable win32 processor
library using MSVC's cl.exe.  I accomplished the build in a cygwin
environment, setting CXX to "cl.exe" and CXXFLAGS to "/nologo /EHsc". 
Because we're mostly using standard C++, only minor changes were needed. 
The most invasive change is an adaptation to support MSVC's
stdext::hash_map instead of G++'s __gnu_cxx::hash_map, complete with a
half-assed hash function.

libtool doesn't know to pass cl.exe an /Fo argument instead of a -o one. 
While building tests and tools, the build will place .obj files in the
current directory, instead of src/processor.  This only happens when
building minidump_dump, minidump_stackwalk, and the unit tests.  When the
build stops at these points, you can move the .obj file from the current
directory into src/processor and run "make" again to resume the build.

Also, this doesn't clean up some MSVC-specific warnings or adapt everything
to Microsoft's "secure" versions of some functions.  And libtool seems to
be calling cygpath improperly, because there's a lot of "cygpath: can't
convert empty path" business.   Like I said, it's a rough first cut.  I'm
putting it here because it's a better spot for it than living on my
computer, and someone else might find it useful.

Original issue reported on code.google.com by mmento...@gmail.com on 27 Oct 2006 at 7:34

Attachments:

• airbag.63.1.patch

[GoogleCodeExporter]

IS it possible to build native win32 with MinGW/MSYS toolchain? AFAIR this way
project files could be even cross-compiled for win32 on POSIX systems. 

Original comment by techtonik@gmail.com on 13 Jan 2007 at 2:41

[GoogleCodeExporter]

For what its worth I was able to build and use the processor tools under Cygwin 
by
using the standard configure script without modification. I assume it used gcc 
for
the build.

Original comment by water...@gmail.com on 12 Nov 2008 at 12:28

[GoogleCodeExporter]

Issue 277 has been merged into this issue.

Original comment by neal...@gmail.com on 22 Feb 2009 at 8:24