[17483] in Kerberos_V5_Development
Re: Proposed platform assumption changes
daemon@ATHENA.MIT.EDU (Nico Williams)
Mon Jan 30 11:51:50 2012
MIME-Version: 1.0
In-Reply-To: <tsl62ft1ht4.fsf@mit.edu>
Date: Mon, 30 Jan 2012 10:20:06 -0600
Message-ID: <CAK3OfOgkKk=JYh35Vc=zFN8oaU-DNMQxJ_nrT=UfGDo3zE2KDQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Sam Hartman <hartmans@mit.edu>
Cc: Danilo Almeida <dalmeida@mit.edu>, krbdev@mit.edu,
Simo Sorce <simo@redhat.com>
Content-Type: text/plain; charset="utf-8"
Errors-To: krbdev-bounces@mit.edu
Content-Transfer-Encoding: 8bit
On Mon, Jan 30, 2012 at 6:44 AM, Sam Hartman <hartmans@mit.edu> wrote:
> I would not recommend mingw for KFW builds.
>
> I might come to recommend automake and libtool as a Windows build
> strategy using msvc as a compiler by the 1.13 time frame. However for
> something intended to be used by a lot of Windows native applications,
> I'd feel uncomfortable depending on mingw. My areas of nervousness
> include debugability, interactions with code signing and manifest
> generation as well as interactions with Windows exception handling.
I believe Windows builds need to support MSVC. If someone did the
work of showing that it is possible to isolate struct initializers to
source files that can be compiled with mingw and linked with the
remainder that is compiled with MSVC, and that the whole just works,
well, I'd be OK -ecstatic- with that.
Nico
--
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
