This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [PATCH 1/4] setup.exe
On Sun, Feb 17, 2013 at 08:20:48PM +0100, Corinna Vinschen wrote:
>On Feb 17 19:44, Achim Gratz wrote:
>> Christopher Faylor writes:
>> >>Sorry, I didn't follow the entire thread. I'm not big in libstdc++
>> >>stuff, but I thought std::regex is part of it by default.
>> >
>> > Me too. Can someone definitively confirm or deny this?
>>
>> The current toolchain based on cygwin definitely doesn't support it and
>> the status of the upstream implementation can be checked here (scroll
>> down to #28):
>>
>> http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.200x
>>
>> The compiler produces the correct symbols (and has been for some time),
>> but the library doesn't implement those functions and you cannot link.
>> There is another status page for g++ that say much the same, sorry I
>> can't find that link right now.
>
>That's really a pity. If we really need regex'es, the most simple code
>could be fetched from NetBSD. It has the advantage to be single-byte
>only. Paths in the distro shouldn't use multi-byte strings anyway.
I just added a regex object to setup.exe. I tested it on Windows and
it seems to work for the simple case. Nothing is using it right now
of course.
(My suggestion of using Cygwin's didn't work well since it relied on
too many pieces from /usr/include)
>OTOH, it might be sufficent for quite some time, if the autodep strings
>are only evaluated as simple filename suffixes:
>
> autodep: .oct .so .dll
>
> autodep: .info .info.gz
>
>Wouldn't that be sufficent and very easy to implement?
This has also already been covered.
We only care about .info files which show up in /usr/share/info. Would
it matter right now for the distro? Probably not. But, there is no
reason to set the bar low if we're adding a new feature. Using regex
allows much more flexibility than the above and doesn't limit future
potential uses.
If using regex is too big a chore then I'll add this feature myself.
cgf