geiman@bimacs.BITNET (geiman mark) (06/11/91)
Hello all, Did anyone succeed in using the CommonView 2 class library for Windows developing under Borland C++ ? I've been using CommonView 2 with Glockenspiel's own C++ translator, but I can't compile a C++ application that uses CommonView with Borland C++. It seems that the name mangling algorythm of Borland C++ is different of Glockenspiel's, and thus Borland's linker can't resolve CommonView's external references in it's import library (CommonView is implemented as a DLL named GLCV20DR.DLL, with it's import library named WCXXCER.LIB) I don't have the CommonView source, so I can't just compile it with Borland C++. Is a special CommonView import library required for working with Borland C++ ? Are there any other pitfalls in working in this setup? Thanks for any help, Mark Geiman geiman@bimacs.cs.biu.ac.il
tim@gistdev.gist.com (Tim Larson) (06/17/91)
geiman@bimacs.BITNET (geiman mark) writes: >Did anyone succeed in using the CommonView 2 class library for Windows >developing under Borland C++ ? Yes. >I've been using CommonView 2 with Glockenspiel's own C++ translator, >but I can't compile a C++ application that uses CommonView with Borland C++. I believe that you will need to obtain the version of CommonView which includes the link libraries for Borland C++. IMHO, If you have purchased the version of CommonView which works with the Glockenspiel Preprocessor, then ImageSoft SHOULD provide you with a free or real cheap upgrade for the version of CommonView which works with Borland C++. Tim Larson tim@gistdev.gist.com