> Compiling the Examples: > > When attempting to compile client programs, I'm scolded with the infamous
> "Unresolved External" errors. I understand this means that there is an > error in the OMF import library I'm trying to use. I've tried "implib"ing > the Xerces DLLs. This proved ineffective in fending off those "unresolved > externals". Next I tried using Borland's "COFF2OMF" program to convert the > import libraries supplied with the Xerces package into usable OMF import > libraries. Again, failure. I decided that the only way I could think of > to get rid of these blasted errors was to compile the Xerces library source > with BCC, because I figured there may have been a Visual C++ induced > annoyance in the DLL supplied with the package. Most C++ compilers have there own name-mangling scheme for names known to the linker. You cannot work around this using these sorts of tools. The only solution is to build the Xerces library with the compiler you want to use. > Compiling the Xerces Source: > Frustrated over my inability to compile the sample programs that came in > the Xerces package, I attempted to compile the Xerces source. And what did > I find when I unzipped the Xerces-src package? I found nice little project > files supporting various C++ compilers, but not the one I was trying to > use. True, there is the BCB4 project, which almost worked except for the > fact that the free Borland compiler does not come with the VCL library, > which is necessary to compile the Xerces BCB project. I had not lost hope > just yet, as I could think of a few different ways in which I could perhaps > avoid the VCL libraries, or perhaps even download them. Alas, all my > efforts were for not, and I finally accepted defeat. > > Now I plead with thee, if you good people could help me resolve my problem, > I would be in your debt. I seem to recall previous postings on the list regarding BCC 5.5. Did you try searching the mail archives for more information? http://marc.theaimsgroup.com/?l=xerces-c-dev Dave "Nicholas G. Lesniewski-Laas" To: [EMAIL PROTECTED] <Rabid_Stick@anime cc: (bcc: David N Bertoni/CAM/Lotus) wired.net> Subject: Xerces with BCC 5.5 10/25/2001 03:44 PM Please respond to xerces-c-dev Hi, I hope I don't come off as sounding stupid or ridiculously ignorant, but I can't for the life of me figure out why I can not compile Xerces client programs, or even Xerces itself, with the free Borland C++ 5.5 compiler. Compiling the Examples: When attempting to compile client programs, I'm scolded with the infamous "Unresolved External" errors. I understand this means that there is an error in the OMF import library I'm trying to use. I've tried "implib"ing the Xerces DLLs. This proved ineffective in fending off those "unresolved externals". Next I tried using Borland's "COFF2OMF" program to convert the import libraries supplied with the Xerces package into usable OMF import libraries. Again, failure. I decided that the only way I could think of to get rid of these blasted errors was to compile the Xerces library source with BCC, because I figured there may have been a Visual C++ induced annoyance in the DLL supplied with the package. Compiling the Xerces Source: Frustrated over my inability to compile the sample programs that came in the Xerces package, I attempted to compile the Xerces source. And what did I find when I unzipped the Xerces-src package? I found nice little project files supporting various C++ compilers, but not the one I was trying to use. True, there is the BCB4 project, which almost worked except for the fact that the free Borland compiler does not come with the VCL library, which is necessary to compile the Xerces BCB project. I had not lost hope just yet, as I could think of a few different ways in which I could perhaps avoid the VCL libraries, or perhaps even download them. Alas, all my efforts were for not, and I finally accepted defeat. Now I plead with thee, if you good people could help me resolve my problem, I would be in your debt. Thank You. --Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
