ports/devel/xsd/files/patch-xsd_doc_xsd.xhtml
Raphael Kubo da Costa f484b5cb28 Update to 4.0.0.
- Get rid of most of our patches: all the build fix patches are now
  unneeded, and the only ones we still have in files/ are there to either
  rename the xsd binary or install files into the right locations.

- Get rid of most bundled dependencies: use devel/build instead of the
  bundled copy, and libcutl via devel/libcutl. The only exception is
  libxsd-frontend, simply because its upstream is too horrible: it does not
  even contain a `make install' target.

- Expand the LICENSE part: the port is GPLv2-licensed, but also contains
  exceptions to allow its use with most free software licenses.

- Set CPPFLAGS, not CXXFLAGS, as the former's where we normally pass
  additional include paths.
2015-09-06 22:14:55 +00:00

75 lines
3.3 KiB
HTML

Rename the xsd binary to xsdcxx, as lang/mono already installs an executable
called `xsd'.
--- xsd/doc/xsd.xhtml.orig 2014-07-21 06:38:41 UTC
+++ xsd/doc/xsd.xhtml
@@ -3,11 +3,11 @@
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
- <title>XSD 4.0.0 Compiler Command Line Manual</title>
+ <title>XSDCXX 4.0.0 Compiler Command Line Manual</title>
<meta name="copyright" content="&copy; 2005-2014 Code Synthesis Tools CC"/>
<meta name="keywords" content="xsd,xml,schema,c++,mapping,data,binding,code,generator,manual,man,page"/>
- <meta name="description" content="XSD Compiler Command Line Manual"/>
+ <meta name="description" content="XSDCXX Compiler Command Line Manual"/>
<link rel="stylesheet" type="text/css" href="default.css" />
@@ -50,19 +50,19 @@
<h1>NAME</h1>
- <p>xsd - W3C XML Schema to C++ Compiler</p>
+ <p>xsdcxx - W3C XML Schema to C++ Compiler</p>
<h1>SYNOPSIS</h1>
<dl id="synopsis">
- <dt><code><b>xsd</b> <i>command</i> [<i>options</i>] <i>file</i> [<i>file</i> ...]</code></dt>
- <dt><code><b>xsd help</b> [<i>command</i>]</code></dt>
- <dt><code><b>xsd version</b></code></dt>
+ <dt><code><b>xsdcxx</b> <i>command</i> [<i>options</i>] <i>file</i> [<i>file</i> ...]</code></dt>
+ <dt><code><b>xsdcxx help</b> [<i>command</i>]</code></dt>
+ <dt><code><b>xsdcxx version</b></code></dt>
</dl>
<h1>DESCRIPTION</h1>
- <p><code><b>xsd</b></code> generates vocabulary-specific, statically-typed
+ <p><code><b>xsdcxx</b></code> generates vocabulary-specific, statically-typed
C++ mapping from W3C XML Schema definitions. Particular mapping to
produce is selected by a <code><i>command</i></code>. Each mapping has
a number of mapping-specific <code><i>options</i></code> that should
@@ -138,10 +138,10 @@
<p>When the C++11 mode is selected, you normally don't need to perform any
extra steps other than enable C++11 in your C++ compiler, if required. The
- XSD compiler will automatically add the necessary macro defines to the
- generated header files that will switch the header-only XSD runtime library
+ XSDCXX compiler will automatically add the necessary macro defines to the
+ generated header files that will switch the header-only XSDCXX runtime library
(<code><b>libxsd</b></code>) to the C++11 mode. However, if you include any
- of the XSD runtime headers directly in your application (normally you just
+ of the XSDCXX runtime headers directly in your application (normally you just
include the generated headers), then you will need to define the
<code><b>XSD_CXX11</b></code> macro for your entire project.</p></dd>
@@ -219,7 +219,7 @@
<p>For example, if you have file <code><b>hello.xsd</b></code> with
namespace <code><b>http://example.com/hello</b></code> and you run
- <code><b>xsd</b></code> on this file, then the string in question will
+ <code><b>xsdcxx</b></code> on this file, then the string in question will
be:</p>
<p><code><b>hello.xsd. http://example.com/hello</b></code></p>
@@ -1530,7 +1530,7 @@ namespace .*
<h1>DIAGNOSTICS</h1>
<p>If the input file is not a valid W3C XML Schema definition,
- <code><b>xsd</b></code> will issue diagnostic messages to STDERR
+ <code><b>xsdcxx</b></code> will issue diagnostic messages to STDERR
and exit with non-zero exit code.</p>
<h1>BUGS</h1>