You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

100 lines
4.3 KiB

  1. <?xml version="1.0" ?>
  2. <!--
  3. * Licensed to the Apache Software Foundation (ASF) under one or more
  4. * contributor license agreements. See the NOTICE file distributed with
  5. * this work for additional information regarding copyright ownership.
  6. * The ASF licenses this file to You under the Apache License, Version 2.0
  7. * (the "License"); you may not use this file except in compliance with
  8. * the License. You may obtain a copy of the License at
  9. *
  10. * http://www.apache.org/licenses/LICENSE-2.0
  11. *
  12. * Unless required by applicable law or agreed to in writing, software
  13. * distributed under the License is distributed on an "AS IS" BASIS,
  14. * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  15. * See the License for the specific language governing permissions and
  16. * limitations under the License.
  17. -->
  18. <!DOCTYPE faqs SYSTEM "sbk:/style/dtd/faqs.dtd">
  19. <faqs title="Distributing &XercesCName;">
  20. <faq title="Can I use &XercesCName; in my product?">
  21. <q>Can I use &XercesCName; in my product?</q>
  22. <a>
  23. <p>Most likely yes. &XercesCName; is distributed under
  24. the terms of the Apache Software License version 2.0
  25. which is a fairly permissive license. In particular,
  26. it allows you to distribute your application in
  27. binary form without requiring you to also release
  28. the source code. Read the license agreement for more
  29. information and if you still have further questions,
  30. then please address them to the
  31. <jump href="&MailURI;">&XercesCName; user mailing list</jump>.</p>
  32. </a>
  33. </faq>
  34. <faq title="Which files do I need to distribute with my application?">
  35. <q>Which files do I need to distribute with my application?</q>
  36. <a>
  37. <p>You only need to distribute <em>one</em> file:<br></br>
  38. &XercesC3WindowsDLL;.dll for Windows<br/>
  39. &XercesC3UnixLib;-&XercesC3UnixSoVersion;.a for AIX<br/>
  40. &XercesC3UnixLib;-&XercesC3UnixSoVersion;so. for Solaris/Linux<br/>
  41. &XercesC3UnixLib;-&XercesC3UnixSoVersion;.sl for HP-UX on PA-RISC<br/>
  42. &XercesC3UnixLib;-&XercesC3UnixSoVersion;.so for HP-UX on IA64<br/>
  43. &XercesC3UnixLib;-&XercesC3UnixSoVersion;.dylib for Mac OS X
  44. </p>
  45. <p>Note, however, that if you built &XercesCName; with dependencies
  46. on other libraries (e.g., ICU for transcoder support or libcurl
  47. for net accessor support) then you will need to ship those
  48. libraries as well.</p>
  49. <p>You can also link your application to a static version
  50. of the &XercesCName; library in which case you won't need
  51. to distribute any extra libraries.</p>
  52. </a>
  53. </faq>
  54. <faq title="I do not see a binary for my platform. When will it be available?">
  55. <q>I do not see a binary for my platform. When will it be available?</q>
  56. <a>
  57. <p>The reason why you see binaries only for some specific
  58. platforms is that we have had the maximum requests for
  59. them. Moreover, we have limited resources and hence cannot
  60. publish binaries for every platform. If you wish to
  61. contribute your time and effort in building binaries for a
  62. specific platform/environment then please send a mail to the
  63. <jump href="&MailURI;">&XercesCName; developer mailing list</jump>.</p>
  64. </a>
  65. </faq>
  66. <faq title="When will a port to my platform be available?">
  67. <q>When will a port to my platform be available?</q>
  68. <a>
  69. <p>We would like to see &XercesCName; ported to as
  70. many platforms as practical. However, due to limited resources
  71. we cannot do all the ports. Here are the <jump
  72. href="program-others-&XercesC3Series;.html#PortingGuidelines">Porting
  73. Guidelines</jump>.</p>
  74. <p>We encourage you to submit the changes that
  75. are required to make it work on another platform. We will
  76. incorporate these changes in the source code base and make
  77. them available in the future releases.</p>
  78. <p>All porting changes may be sent to the
  79. <jump href="&MailURI;">&XercesCName; developer mailing list</jump>
  80. .</p>
  81. </a>
  82. </faq>
  83. </faqs>