diff --git a/Makefile b/Makefile new file mode 100644 --- /dev/null +++ b/Makefile @@ -0,0 +1 @@ +include ../Makefile.common diff --git a/abi_used_libs b/abi_used_libs new file mode 100644 --- /dev/null +++ b/abi_used_libs @@ -0,0 +1,4 @@ +libc.so.6 +libgcc_s.so.1 +libstdc++.so.6 +libxerces-c-3.1.so diff --git a/files/xsdcxx-rename.patch b/files/xsdcxx-rename.patch new file mode 100644 --- /dev/null +++ b/files/xsdcxx-rename.patch @@ -0,0 +1,153 @@ +Index: trunk/xsd/doc/xsd.1 +=================================================================== +--- a/xsd/doc/xsd.1 ++++ b/xsd/doc/xsd.1 +@@ -1,16 +1,16 @@ + .\" Process this file with + .\" groff -man -Tascii xsd.1 + .\" +-.TH XSD 1 "July 2014" "XSD 4.0.0" ++.TH XSDCXX 1 "July 2014" "XSDCXX 4.0.0" + .SH NAME +-xsd \- W3C XML Schema to C++ Compiler ++xsdcxx \- W3C XML Schema to C++ Compiler + .\" + .\" + .\" + .\"-------------------------------------------------------------------- + .SH SYNOPSIS + .\"-------------------------------------------------------------------- +-.B xsd ++.B xsdcxx + .I command + .B [ + .I options +@@ -20,19 +20,19 @@ + .I file + .B ...] + .in +-.B xsd help ++.B xsdcxx help + .B [ + .I command + .B ] + .in +-.B xsd version ++.B xsdcxx version + .\" + .\" + .\" + .\"-------------------------------------------------------------------- + .SH DESCRIPTION + .\"-------------------------------------------------------------------- +-.B xsd ++.B xsdcxx + generates vocabulary-specific, statically-typed C++ mapping from W3C XML + Schema definitions. Particular mapping to produce is selected by a + .IR command . +@@ -96,7 +96,7 @@ + .PP + .RS + .RS 3 +-.B xsd help ++.B xsdcxx help + .I command + .RE + .PP +@@ -133,9 +133,9 @@ + + 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 +-(\fBlibxsd\fP) to the C++11 mode\. However, if you include any of the XSD ++XSDCXX compiler will automatically add the necessary macro defines to the ++generated header files that will switch the header-only XSDCXX runtime library ++(\fBlibxsd\fP) to the C++11 mode\. However, if you include any of the XSDCXX + runtime headers directly in your application (normally you just include the + generated headers), then you will need to define the \fBXSD_CXX11\fP macro + for your entire project\. +@@ -1632,7 +1632,7 @@ + .\" + .SH DIAGNOSTICS + If the input file is not a valid W3C XML Schema definition, +-.B xsd ++.B xsdcxx + will issue diagnostic messages to + .B STDERR + and exit with non-zero exit code. +Index: trunk/xsd/doc/xsd.xhtml +=================================================================== +--- a/xsd/doc/xsd.xhtml ++++ b/xsd/doc/xsd.xhtml +@@ -3,11 +3,11 @@ + + + +- XSD 4.0.0 Compiler Command Line Manual ++ XSDCXX 4.0.0 Compiler Command Line Manual + + + +- ++ + + + +@@ -50,19 +50,19 @@ + +

NAME

+ +-

xsd - W3C XML Schema to C++ Compiler

++

xsdcxx - W3C XML Schema to C++ Compiler

+ +

SYNOPSIS

+ +
+-
xsd command [options] file [file ...]
+-
xsd help [command]
+-
xsd version
++
xsdcxx command [options] file [file ...]
++
xsdcxx help [command]
++
xsdcxx version
+
+ +

DESCRIPTION

+ +-

xsd generates vocabulary-specific, statically-typed ++

xsdcxx generates vocabulary-specific, statically-typed + C++ mapping from W3C XML Schema definitions. Particular mapping to + produce is selected by a command. Each mapping has + a number of mapping-specific options that should +@@ -138,10 +138,10 @@ + +

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 + (libxsd) 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 + XSD_CXX11 macro for your entire project.

+ +@@ -219,7 +219,7 @@ + +

For example, if you have file hello.xsd with + namespace http://example.com/hello and you run +- xsd on this file, then the string in question will ++ xsdcxx on this file, then the string in question will + be:

+ +

hello.xsd. http://example.com/hello

+@@ -1530,7 +1530,7 @@ +

DIAGNOSTICS

+ +

If the input file is not a valid W3C XML Schema definition, +- xsd will issue diagnostic messages to STDERR ++ xsdcxx will issue diagnostic messages to STDERR + and exit with non-zero exit code.

+ +

BUGS

diff --git a/package.yml b/package.yml new file mode 100644 --- /dev/null +++ b/package.yml @@ -0,0 +1,23 @@ +name : xsd +version : 4.0.0 +release : 1 +source : + - http://www.codesynthesis.com/download/xsd/4.0/xsd-4.0.0+dep.tar.bz2 : eca52a9c8f52cdbe2ae4e364e4a909503493a0d51ea388fc6c9734565a859817 +license : GPL-2.0 +component : programming.tools +summary : CodeSynthesis XSD is an W3C XML Schema to C++ data binding compiler +description: | + CodeSynthesis XSD is an open-source, cross-platform W3C XML Schema to C++ data binding compiler. Provided with an XML instance specification (XML Schema), it generates C++ classes that represent the given vocabulary as well as XML parsing and serialization code. You can then access the data stored in XML using types and functions that semantically correspond to your application domain rather than dealing with the intricacies of reading and writing XML. +builddeps : + - pkgconfig(libcutl) + - pkgconfig(xerces-c) + - libboost-devel +setup : | + %patch -p1 < $pkgfiles/xsdcxx-rename.patch +build : | + %make BOOST_LINK_SYSTEM=y EXTERNAL_LIBCUTL=y +install : | + make install_prefix=$installdir/usr install + # Rename files to xsdcxx to avoid name conflicts with mono + mv $installdir/usr/bin/xsd{,cxx} + mv $installdir/usr/share/man/man1/xsd{,cxx}.1 diff --git a/pspec_x86_64.xml b/pspec_x86_64.xml new file mode 100644 --- /dev/null +++ b/pspec_x86_64.xml @@ -0,0 +1,49 @@ + + + xsd + + Peter O'Connor + peter@solus-project.com + + GPL-2.0 + programming.tools + CodeSynthesis XSD is an W3C XML Schema to C++ data binding compiler + CodeSynthesis XSD is an open-source, cross-platform W3C XML Schema to C++ data binding compiler. Provided with an XML instance specification (XML Schema), it generates C++ classes that represent the given vocabulary as well as XML parsing and serialization code. You can then access the data stored in XML using types and functions that semantically correspond to your application domain rather than dealing with the intricacies of reading and writing XML. + + https://solus-project.com/sources/README.Solus + + + xsd + CodeSynthesis XSD is an W3C XML Schema to C++ data binding compiler + CodeSynthesis XSD is an open-source, cross-platform W3C XML Schema to C++ data binding compiler. Provided with an XML instance specification (XML Schema), it generates C++ classes that represent the given vocabulary as well as XML parsing and serialization code. You can then access the data stored in XML using types and functions that semantically correspond to your application domain rather than dealing with the intricacies of reading and writing XML. + + programming.tools + + /usr/bin + /usr/share/doc + /usr/share/man + + + + xsd-devel + Development files for xsd + CodeSynthesis XSD is an open-source, cross-platform W3C XML Schema to C++ data binding compiler. Provided with an XML instance specification (XML Schema), it generates C++ classes that represent the given vocabulary as well as XML parsing and serialization code. You can then access the data stored in XML using types and functions that semantically correspond to your application domain rather than dealing with the intricacies of reading and writing XML. + + programming.devel + + xsd + + + /usr/include/ + + + + + 2017-06-30 + 4.0.0 + Packaging update + Peter O'Connor + peter@solus-project.com + + + \ No newline at end of file