[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [groff] Loss of MSVC support
From: |
Colin Watson |
Subject: |
Re: [groff] Loss of MSVC support |
Date: |
Thu, 14 Feb 2019 12:50:09 +0000 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Wed, Feb 13, 2019 at 06:58:18PM +0200, Eli Zaretskii wrote:
> Just to make what Keith says (and I concur) crystal clear: there's a
> need to distinguish between C99 compliance of the compiler and the
> C99/Posix compliance of the C runtime. We can assume the former,
> certainly when using MinGW GCC, but we cannot assume the latter when
> building a native MS-Windows port (as opposed to Cygwin port) of
> Groff.
If it's just the runtime, then Gnulib should be able to paper over a
pretty fair number of the differences, and groff already uses that. It
may just be a matter of somebody who can do test-builds on Windows
making sure that we're importing the right set of Gnulib modules.
(It's possible that some of the _WIN32 conditionals can be supplied by
Gnulib these days, but there's also no great urgency to remove them,
IMO.)
--
Colin Watson address@hidden
- [groff] Loss of MSVC support, Eric S. Raymond, 2019/02/12
- Re: [groff] Loss of MSVC support, Keith Marshall, 2019/02/12
- Re: [groff] Loss of MSVC support, Eric S. Raymond, 2019/02/12
- Re: [groff] Loss of MSVC support, Keith Marshall, 2019/02/12
- Re: [groff] Loss of MSVC support, Eric S. Raymond, 2019/02/12
- Re: [groff] Loss of MSVC support, Eli Zaretskii, 2019/02/13
- Re: [groff] Loss of MSVC support,
Colin Watson <=
- Re: [groff] Loss of MSVC support, John Gardner, 2019/02/14
- Re: [groff] Loss of MSVC support, Walter Harms, 2019/02/14
- Re: [groff] Loss of MSVC support, Eli Zaretskii, 2019/02/14
- Re: [groff] Loss of MSVC support, Colin Watson, 2019/02/14
- Re: [groff] Loss of MSVC support, John Gardner, 2019/02/14
- Re: [groff] Loss of MSVC support, Eli Zaretskii, 2019/02/15