🚀 go-pugleaf

Borland has made available a brief white paper that outlines the
few steps needed to build MFC (and applications) with BCC 3.1.  This
paper is available from Compu$erve, and I believe you can also get
it by phoning their technical support.

Steven "MFC guy"


In article <59800002@otter.hpl.hp.com> slo@otter.hpl.hp.com (Steve Loughran) writes:
>
>Has anyone actually managed to build and MFC class library based app
>under BC++3.1 yet?
>
>I had a go yesterday without much success on the bare minimum Helloapp which
>comes with MSC 7.0
>
>To get it to compile I had to add a few lines before including <afxwin.h>:-
>
>	//turn off _seg addressing
>#define BASED_CODE
>
>	//rename RTL functions
>#define _stricmp stricmp
>#define _strupr strupr
>#define _strlwr strlwr
>#define _strrev strrev
>
>I don't know what the magic switch to interpret ambiguities the same way
>as MS is -i guess "use _objectData calling" under optimisations is a likely
>candidate.
>
>However compilation ain't enough : I can't link to the library due to bad
>object file records in SAFXCW.LIB.
>A comparison of object files produced by MSC and BCC seems to indicate that
>they are using different name mangling conventions.
>
>I wouldn't be suprised if I'm going to have to recompile the entire 
>foundation class library to have a hope of getting a simple MFC app to
>work. I also get the sneaking suspicion that from now on sharing .obj files
>from MSC to BCC isnt going to be as easy as it was when I was just importing
>C functions.
>
>	-Steve
>
>


-- 
Steven Sinofsky
stevesi@microsoft.com
Disclaimer: I don't speak for Microsoft, BillG does that.