cl.exe and wxUSE_CRASHREPORT

[Daniel C. Bastos]

In article <XDwgg.A.d2N.3ZSeGB at brage.sunsite.dk>,
Vadim Zeitlin wrote:

> DCB> cl : Command line warning D9002 : ignoring unknown option '-mthreads'
> DCB> pinky.cpp
> DCB> 
> DCB> c:\Program Files\Microsoft Visual Studio 8\VC\INCLUDE\xlocale(326) :
> DCB> warning C4530: C++ exception handler used, but unwind semantics are not
> DCB> enabled. Specify /EHsc
> 
>  Both of these stem from the fact that the flags from wx-config are for g++
> while you need the options for MSVC. Sorry but I really don't understand
> what is your point.
> 
>  To use wx-config with MSVC you need to run configure with MSVC (which
> might or not work, being realistic it probably doesn't), not with g++ and
> then hope that it's just going magically work with a completely different
> compiler.

I was expecting it not to work at the linking phase because the
libraries were made for g++, but what I fed cl was just source code and
paths to include files, no? Shouldn't that be just C++? Since it didn't
go through that stage, I decided to show it here. I was just looking for
an explanation of what's wrong with that stage of compilation.