Re: [MinGW-dvlpr] libunistring

[Erwin W. <wat...@xs...>]

Charles Wilson schreef, Op 12-10-2011 21:21:
> MinGW, at present, doesn't intend to be a repository of all possible
> packages ported to win32.  Right now, the only packages we provide, in
> the -mingw32- subsystem, fall into two categories, with a few historical
> exceptions:
>
> 	1) development tools like auto* (and gcc itself, with its
> 	   supporting libraries, of course).  This includes the
> 	   libiconv and libintl libraries, because they are needed, in
> 	   mingw form, in order for the gettextize tool (&friends) to
> 	   work properly.
> 	2) a few compression libraries (zlib, bzip, xz, libarchive)
> 	   which are needed to support mingw-get.exe development.
>
> Stuff like PDCurses falls under the "historical exception" because long
> ago, there used to be a PDCurses mingwPORT "contrib" item, and somebody
> offered to update it to make it "mingw-get" compatible.

I packaged PDCurses for mingw.

I think that handling Unicode strings is basic functionality nowadays. 
What libc offers in not enough. Libunistring is a good extension.

>
> We haven't really had the discussion about handling additional packages.
>   I think that deserves its own thread, to consider the issues: What do
> we do about "contributed" mingw32 libraries and exes?  Should they even
> be considered for acceptance as part of the mingw.org packageset? Should
> that be a separate project (with its own mingw-get-compatible
> repository?)  OR, should it be managed as an intrinsic part of the
> "core" offerings here @ mingw.org?  Policies&  procedures?

I would like a central repository with all kinds of mingw packages very 
much. My preference would be to have it under mingw, or very close to 
it. This is much better than having packages spread all over the 
internet, or lots of people that struggle with porting the same package.

Until then I will offer libunistring for mingw on my own home page. And 
if you still want it, I package it for mingw.


>
>> I used portmaker to create the mingwPORT scripts. Libunistring compiles
>> without problems, out-of-the-box,
> FYI, you might want to try the new 'mgwport' package -- which should
> allow you to reuse (a lot of) your .cygport scripts from your cygwin
> package.
>
> Unlike portmaker/mingwPORT, mgwport is intended for creating binary
> tarballs for distribution.  mingwPORT, OTOH, is meant for distributing
> "recipes" that end users can use to build the binaries themselves, and
> requires some hacking to make it work for the bindist purpose.

OK. That sounds very good. But as long as there is no intention to take 
libunistring, I will not try it.

-- 
Erwin Waterlander
http://waterlan.home.xs4all.nl/