Stephen Long <[EMAIL PROTECTED]> writes:

> The xerces build does not create a xerces.dll.  Here is the listing
> for the lib directory:
> 
> [EMAIL PROTECTED] ~/download/xerces-c-src_2_3_0/lib
> $ ls -alF
> total 13765
> drwxrwxrwx+   2 sl492591 mkpasswd     4096 Jul  1 16:45 ./
> drwxr-xr-x+  12 sl492591 mkpasswd     4096 Jul  1 15:41 ../
> -rwxrwxrwx    1 sl492591 mkpasswd  4506139 Jul  1 16:45 cygxerces-c23.dll*
> lrwxrwxrwx    1 sl492591 mkpasswd      207 Jul  1 16:45
> libxerces-c.dll.a ->
> 
> /cygdrive/c/download/xerces-c-src_2_3_0/l/libxerces-c2_3_0.dll.a
> -rw-rw-rw-    1 sl492591 mkpasswd   586720 Jul  1 16:44 libxerces-c23.def
> -rw-rw-rw-    1 sl492591 mkpasswd  7265276 Jul  1 16:39 libxerces-c23.dll.a
> -rw-rw-rw-    1 sl492591 mkpasswd  1736299 Jul  1 16:45 libxerces-c23.map
> lrwxrwxrwx    1 sl492591 mkpasswd      197 Jul  1 16:45
> libxerces-c2_3_0.dll.a ->
> 
> /cygdrive/c/download/xerces-c-src_2_0/lib/libxerces-c23.dll.a
> 
> I'll add a link for Xerces.dll.  Should I link it to cygxerces-c23.dll
> or libxerces-c2_3_0.dll.a ?  Or would it best to install the win32
> binary and add its lib dir to the path?

According to one windows user on the list, the name of the file
produced should have been: 

  Xerces-c_2_3_0.dll

I would think that it should link to cygxerces-c23.dll, but I'm not a
windows user.

jas.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to