|
Boost : |
Subject: Re: [boost] config with cygwin
From: Beman Dawes (bdawes_at_[hidden])
Date: 2010-06-14 06:57:00
On Mon, Jun 14, 2010 at 5:29 AM, Robert Jones <robertgbjones_at_[hidden]> wrote:
> On Fri, Jun 11, 2010 at 3:17 PM, Beman Dawes <bdawes_at_[hidden]> wrote:
>
>> Robert wrote:
>>
>> > I've recently upgraded to the lastest version of Cygwin and found that
>> > this current version supports wchar_t, wstring, etc
>>
>> Yes! Finally! MinGW also now supports them. Filesystem V3 requires
>> wchar_t, wstring, etc., and all the tests pass with both Cygwin and
>> MinGW.
>>
>>
> I can't recall the details, but IIRC there was chatter a while back that
> due to limitations of Cygwin/MinGW you'd decided drop full support for
> these platforms from Boost.Filesystem.
Yes, and as a result the code became much cleaner and easier to
write/read/debug.
At that time, several Boosters asked the Cygwin folks for wide
character support, and they gave that long standing issue higher
priority soon afterwords.
> Assuming my recollections are broadly correct, does this latest development
> now mean that Cygwin/MinGW are again fully supported by Boost.Filesystem.
Yes, I've been testing filesystem on both Cygwin and MinGW (downloaded
directly, not via Cygwin) from the Windows command line. All tests are
passing on Cygwin, and all tests are passing on MinGW with static
linking. I fairly sure the dynamic linking problem with MinGW is their
problem, not a Boost problem.
I haven't tested filesystem from the cygwin/bash command line, so if
someone wants to test trunk in that environment I'd like to hear about
the results.
Thanks for the interest,
--Beman
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk