Hi Wendy, To get xerces-c 2.1 built under cygwin, you should call runConfigure like so: > runConfigure -pcygwin -cgcc -xg++
then you do your "make" and "make install". Something you may want to keep in mind is that in the final step of "make", where it actually links all the .o files to create the xerces dll, that you may get crashes in the gcc build tools. To get around this, make sure there aren't any cygwin apps or shells running except for the shell that you are running make in. Then, you need to make sure that cygwin has a certain registry value set, which I do with the following: > regtool.exe -i set /HKCU/Software/Cygnus\ Solutions/Cygwin/heap_chunk_in_mb 0x400 Also, make sure that you have gcc 3.2 installed. This was made available this week for cygwin in a non-test version. I'm currently waiting for approval on getting a xerces-c and xerces-c-devel package into the setup.exe process of installing packages that cygwin uses. When this is approved and reviewed, it should be much simpler to get xerces for cygwin without having to build it first :) As far as your linking woes, keep in mind that when building applications that link to dlls and the dll exposes a c++ type, you will have problems because different compiler vendors use different formats for exporting c++ types. In other words, the xerces dll that you have on your system that works with VC++ will not work with gcc. -Abe ----- Original Message ----- > I have a set of CPP classes that compile and run fine under VC++ using > xercesc 2.1. I need to port these to AIX and fingured that since access to > that system is not always possible a good intermediate step would be to get > things to build under cygwin on my own machine (Win 2000). > > No matter what I try, I can't resolve the link errors (that's if I can even > get my guess at the right library to be found during linking). I have tried > just about every reasonable name in a -l argument, as well as just putting > the file on the compile line since it has an unknown suffix and should thus > just get linked in. > > Nothing is working. > > So I figured I would try to build the library myself, but couldn't get past > runConfigure. The configure.log file says that a.exe can't be executed, but > I am unable to determine why. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
