Most likely yes. &XercesCName; is distributed under the terms of the Apache Software License version 2.0 which is a fairly permissive license. In particular, it allows you to distribute your application in binary form without requiring you to also release the source code. Read the license agreement for more information and if you still have further questions, then please address them to the &XercesCName; user mailing list.

You only need to distribute one file:

&XercesC3WindowsDLL;.dll for Windows
&XercesC3UnixLib;-&XercesC3UnixSoVersion;.a for AIX
&XercesC3UnixLib;-&XercesC3UnixSoVersion;so. for Solaris/Linux
&XercesC3UnixLib;-&XercesC3UnixSoVersion;.sl for HP-UX on PA-RISC
&XercesC3UnixLib;-&XercesC3UnixSoVersion;.so for HP-UX on IA64
&XercesC3UnixLib;-&XercesC3UnixSoVersion;.dylib for Mac OS X

Note, however, that if you built &XercesCName; with dependencies on other libraries (e.g., ICU for transcoder support or libcurl for net accessor support) then you will need to ship those libraries as well.

You can also link your application to a static version of the &XercesCName; library in which case you won't need to distribute any extra libraries.

The reason why you see binaries only for some specific platforms is that we have had the maximum requests for them. Moreover, we have limited resources and hence cannot publish binaries for every platform. If you wish to contribute your time and effort in building binaries for a specific platform/environment then please send a mail to the &XercesCName; developer mailing list.

We would like to see &XercesCName; ported to as many platforms as practical. However, due to limited resources we cannot do all the ports. Here are the Porting Guidelines.

We encourage you to submit the changes that are required to make it work on another platform. We will incorporate these changes in the source code base and make them available in the future releases.

All porting changes may be sent to the &XercesCName; developer mailing list .