[17486] in Kerberos_V5_Development
Re: Proposed platform assumption changes
daemon@ATHENA.MIT.EDU (Sam Hartman)
Mon Jan 30 12:32:57 2012
From: Sam Hartman <hartmans@mit.edu>
To: Nico Williams <nico@cryptonector.com>
Date: Mon, 30 Jan 2012 12:32:42 -0500
In-Reply-To: <CAK3OfOgkKk=JYh35Vc=zFN8oaU-DNMQxJ_nrT=UfGDo3zE2KDQ@mail.gmail.com>
(Nico Williams's message of "Mon, 30 Jan 2012 10:20:06 -0600")
Message-ID: <tslhazdxfid.fsf@mit.edu>
MIME-Version: 1.0
Cc: Danilo Almeida <dalmeida@mit.edu>, krbdev@mit.edu,
Simo Sorce <simo@redhat.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
>>>>> "Nico" == Nico Williams <nico@cryptonector.com> writes:
Nico> I believe Windows builds need to support MSVC.
Why? I believe that the resulting SDK needs to work on applications
built with msvc. But why does MIT Kerberos need to support msvc for
Windows development? I can see a number of reasons, but the issue
really seems subject to enumeration of what a proposal to use mingw
should have to support.
I'm skeptical of "you must support this," but very likely to believe "to
use mingw you'd have to show that x y and z are not a problem."
Part of what I'm saying is that there a fairly small number of people
who are going to build KFW, getting the environment set up is already
tricky, and reducing KFW's build dependencies would probably not be the
most important thing on my list of things to optimize for in future KFW
work.
However, making sure you can debug on Windows and similar issues like
that seem very important.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
