Greetings!

 

Issues with Cygwin Build:

 

Background:

 

I have successfully added socket-level support to the Xerces 2.3 code base

under Windows.  This support builds and works just fine with VC6, creating

a Windows DLL which links and operates with my applications.

 

I am now attempting to add this support to the Xerces 2.3 Unix code base

and have successfully compiled this support under CYGWIN_NT-5.1

(after removing the default Cygwin xerces development library L  ).

 

Unfortunately, I get undefined externals when the Cygwin xerces shared

library is built of the form shown below.  I got no undefined references

with the vanilla xerces 2_3_0 distribution.

 

Questions:

 

  1. How does one add an additional library to the Cygwin shared library build?
  2. The first library built.  Is the second necessary?
  3. Any suggestions about how I might resolve this?
  4. Again, is there any interest from the group with respect to adding socket support to the

Xerces release baseline?

 

TIA and have a great weekend!

 

Errors from build.

 

Building /cygdrive/c/xercestmp/xerces-c-src_2_3_0.unx/lib/libxerces-c2_3_0.dll

Building /cygdrive/c/xercestmp/xerces-c-src_2_3_0.unx/lib/cygxerces-c23.dll

Warning: resolving [EMAIL PROTECTED] by linking to _gethostbyname

Use --enable-stdcall-fixup to disable these warnings

Use --disable-stdcall-fixup to disable these fixups

Warning: resolving [EMAIL PROTECTED] by linking to _inet_addr

Warning: resolving [EMAIL PROTECTED] by linking to _gethostbyaddr

Warning: resolving [EMAIL PROTECTED] by linking to _socket

Warning: resolving [EMAIL PROTECTED] by linking to _shutdown

Creating library file: /cygdrive/c/xercestmp/xerces-c-src_2_3_0.unx/lib/libxerce

s-c23.dll.a

CYGWIN/BinSocketInputStream.o(.text+0x476):BinSocketInputStream.cpp: undefined r

eference to [EMAIL PROTECTED]'

 

 

 

Gilbert T. Williams

Sr. Systems Engineer

ImageGuide, Inc.

1629 Thames St. Ste 200A

Baltimore, MD 21231

(v) 410.534.1239x104

(f) 410.534.1362

[EMAIL PROTECTED]

www.imageguide.us

 

Reply via email to