cl.exe and wxUSE_CRASHREPORT

[Daniel C. Bastos]

In article <20070620225134.00007e6f at saturn>,
Daniel C. Bastos wrote:

> In article <-iCMiC.A.2WO.3paeGB at brage.sunsite.dk>,
> Vadim Zeitlin wrote:
> 
> > On Wed, 20 Jun 2007 18:21:15 -0400 "Daniel C. Bastos" <dbast0s at yahoo.com.br> wrote:
> > 
> > DCB> >  To use wx-config with MSVC you need to run configure with MSVC (which
> > DCB> > might or not work, being realistic it probably doesn't), not with g++ and
> > DCB> > then hope that it's just going magically work with a completely different
> > DCB> > compiler.
> > DCB> 
> > DCB> I was expecting it not to work at the linking phase because the
> > DCB> libraries were made for g++, but what I fed cl was just source code and
> > DCB> paths to include files, no?
> > 
> >  No. C++ compiler options are not limited to /D and /I.

Thanks for your help. Just for the record, I was able to compile: I
reread the appendix A of the wx book and figured out what I had to do;
also peeked at how vc++ and dialogblocks do it.

%cl -nologo -EHsc -I/c/mgwx/include/msvc -I/c/mgwx/include -D_DEBUG
-I/c/s dk/include -DWIN32 -D__WXMSW__ -DWINDOWS -D_WXDEBUG_ -MDd -c *.cpp

Some warnings show up which can be turned off with -W0, if that's one
would want. To link, I did:

%link -nologo -OUT:out.exe -LIBPATH:"c:/sdk/lib"
-LIBPATH:"c:/mgwx/lib/vc_ lib" -SUBSYSTEM:WINDOWS wxmsw28d_core.lib
wxbase28d.lib kernel32.lib user32.lib gdi32.lib shell32.lib comdlg32.lib
ole32.lib oleaut32.lib advapi32.lib comctl3 2.lib rpcrt4.lib *.obj

I don't quite understand the work of msys, and while I was able to use
the UNIX pathname for the includes in the cl command line, I was not in
the link command line.