[Ant-contrib-developers] Re: Ant bug 20915

[Curt A. <ca...@ho...>]

Since this is the second time this has come up in a week, it is a clear 
sign that I need to document this behavior better and maybe provide a 
URL as part of the exception message.

<libset> and <syslibset> are explicitly for libraries where the file
 name follows a set of linker specific patterns.  If your module name was
 "foo", a ld-style linker would look for files libfoo.a, libfoo.so,
 libfoo.sl, etc and a MSVC-style linker would look for foo.lib.

In almost all instances, a module name starting with "lib" would 
indicate a misunderstanding of the <libset/> behavior, hence the 
exception.  If the exception was removed and "libxerces-c2_2_0", a ld 
link would look for "liblibxerces-c2_2_0.so" and a  Microsoft style link 
would look for "libxerces-c2_2_0.dll".  In  your case, the right module 
name is "xerces-c2_2_0" which will link with libxerces-c2_2_0.so on ld 
style links and xerces-c2_2_0.dll on Microsoft style links.
 
 If your library does not follow the linker specific pattern, you can
 just add it into the main body fileset and any files that are not
 processed by any of the compilers will be sent to the linker.

<cc...>
   ...
   <fileset dir="${lib.dir}" includes="libxerces-c2_2_0.dll"/>
</cc>

FYI: I'm starting a two week vacation tomorrow and I hope to spend some 
time on cpptasks.