From: "Stefan Köpsell" <stefan.koepsell@tu-dresden.de>
To: "'Yaakov Selkowitz'" <yselkowitz@cygwin.com>, <cygwin-apps@cygwin.com>
Subject: AW: [ITP] Mini-XML (mxml)
Date: Sat, 30 Dec 2017 13:02:00 -0000 [thread overview]
Message-ID: <002101d3816e$5e91de80$1bb59b80$@tu-dresden.de> (raw)
In-Reply-To: <c3f65129-e696-72bd-8d8f-f67ea3b305c3@cygwin.com>
Hello,
thanks for your advice.
> Do you plan on ITPing something which uses this? A library by itself is of little use.
Hm, not at the moment. But several of our projects depend on the library - and it makes contributing more easy, if the library is available as Cygwin package.
>Several problems:
>* The source package (NAME) should be name mxml;
>* A shared library should be created (pass --enable-shared to cygconf);
>* Static libraries are not generally desired;
>* There should be 2-3 subpackages, mxml with any program/utilties,
>ibmxml1 with the runtime library, and libmxml-devel (not -dev) with the headers, import library, etc.
There a now two packages: one containing the shared library and the other containing the development files
See: https://sk13.xyz:45443/cygwin/x86/
Sincerely,
Stefan
-----Ursprüngliche Nachricht-----
Von: cygwin-apps-owner@cygwin.com [mailto:cygwin-apps-owner@cygwin.com] Im Auftrag von Yaakov Selkowitz
Gesendet: Freitag, 22. Dezember 2017 21:37
An: cygwin-apps@cygwin.com
Betreff: Re: [ITP] Mini-XML (mxml)
On 2017-12-22 12:49, Stefan Köpsell wrote:
> I am interested in becoming a package maintainer for the Mini-XML
> library (http://michaelrsweet.github.io/mxml/).
>
> Mini-XML is a small XML parsing library that you can use to read XML
> and XML-like data files in your application without requiring large
> non-standard libraries.
Do you plan on ITPing something which uses this? A library by itself is of little use.
> I have tried to make a first package and uploaded it here:
> https://sk13.xyz:45443/cygwin/x86/libmxml-dev/
>
> I would be thankful for any hints regarding issues / quality
> improvements with this package.
Several problems:
* The source package (NAME) should be name mxml;
* A shared library should be created (pass --enable-shared to cygconf);
* Static libraries are not generally desired;
* There should be 2-3 subpackages, mxml with any program/utilties,
libmxml1 with the runtime library, and libmxml-devel (not -dev) with the headers, import library, etc.
--
Yaakov
next prev parent reply other threads:[~2017-12-30 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00d101d37b54$5d9b3b40$18d1b1c0$@tu-dresden.de>
2017-12-22 18:49 ` Stefan Köpsell
2017-12-22 20:36 ` Yaakov Selkowitz
2017-12-30 13:02 ` Stefan Köpsell [this message]
2018-01-09 7:07 AW: " Stefan Köpsell
2018-01-09 18:52 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002101d3816e$5e91de80$1bb59b80$@tu-dresden.de' \
--to=stefan.koepsell@tu-dresden.de \
--cc=cygwin-apps@cygwin.com \
--cc=yselkowitz@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).