Building under Visual Studio 2015
Greg Hudson
ghudson at mit.edu
Sat May 7 20:00:48 EDT 2016
On 05/06/2016 09:21 AM, Chris Kingsley wrote:
> 1. In src/lib/Makefile.in - it was not handling debug builds properly. It should look like this:
>
> ##WIN32##!if defined(VISUALSTUDIOVERSION) && $(VISUALSTUDIOVERSION:.=) >= 140
> ##WIN32##!ifdef NODEBUG
> ##WIN32##WINCRTEXTRA = ucrt.lib vcruntime.lib
> ##WIN32##!else
> ##WIN32##WINCRTEXTRA = ucrtd.lib vcruntimed.lib
> ##WIN32##!endif
> ##WIN32##!endif
That's very helpful; I had run into this problem with debugging builds
before, and didn't know how to fix it. (However, we don't want the
consolidated VISUALSTUDIOVERSION conditional; see
https://github.com/krb5/krb5/commit/0533ebf04d6ab98ccb18652466ea910600bab219
)
With this fixed, our master branch builds under VS2015 with NO_LEASH=1.
> // fp->_flag = 0; doesn't build under VS2015.
We'll figure out a fix for this.
I have been testing with appveyor (which provides a Travis-like
continuous integration service for Windows), and have encountered a
third problem:
uicc.exe kfwribbon.xml kfwribbon.bml /res:kfwribbon.rc
/header:kfwribbon.h /name:KFW_RIBBON
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Windows
Kits\10\bin\x86\uicc.exe"' : return code '0xc0000139'
which may just mean that the VS2015 Community Edition on the appveyor
VMs isn't sufficient to build Leash; I'm not sure.
More information about the kfwdev
mailing list