From: brock_peabody (bpyama_at_[hidden])
Date: 2003-10-15 09:14:23
--- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
> Hi Brock,
> Frankly, I don't know. If any of this options are *required* for
msvc, we can
> put it there. But since you mention that there's global MFC vs.
It's a real pain. Basically, from what I understand, code that uses
MFC can't be linked with code that doesn't.
>seems like we need a new feature, or a new value of
> "<user-interface>" feature.
Yeah, and you can have non-MFC using GUI's and MFC using console
> BTW, what those options do?
I just compared the command line I saw in Visual Studio with the one
generate by bjam. Here is what they mean:
/D "_LIB" /D "_AFXDLL" /D "_MBCS"
/D defines a preprocessor symbol
_LIB - I can't find any info for this one.
_AFXDLL - specifies that you are dynamically linking to MFC. It
seems odd that this has to be specified at compile time.
_MBCS - specifies support for multi-byte character sets.
Actually, after further testing, the only one needed is /D "_AFXDLL".
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk