Hello Ben,
On 2017-02-14 07:45, Benjamin Kaduk wrote: > (FWIW, there is > currently a windows builder that was set up by Alejandro Sedeno > on a VM donated by MIT: > https://buildbot.openafs.org/buildslaves/win7-amd64 . But there is It would be nice to know what software versions Alejandro used for his slave. Taking a quick look in his build log I can imagine he has VS2005 and Platform SDK 7.0 installed. In contrast, I went with VS2008 and Platform SDK 6.0a, trying to be as close to the Secure Endpoints mentioned setup as possible and work from there. > The binaries produced on the buildbots are not distributed, yes. Good :) > It seems that at least sometimes, the historical usage has been to > have a different ntbuild.bat for each of the four combinations of > 32/64-bit and debug/release builds (sometimes called free/checked). > But it probably doesn't matter which one you start off with. At least for the 32/64 bit variation it seems that a separate ntbuild.bat should be used, or the current one be coded better. For the debug/release one there seems to be a command line parameter supported: free/checked > > That one may be a bit harder to find. (I don't even know what the > redistributable status of such a thing would be even if someone did > have a copy sitting around...) Well, I gave up on it :) Instead commented the #include in cm_nls.c and added a typedef for _NORM_FORM enum copied out of the MS documentation. Amazingingly, this was enough for the build to proceed and end in success. Well, at least my openafs/dest directory is now populated and I could at least run "pts help" and "fs help". Haven't bother installing the tools for building the doc tree. I don't think Alejandro is either... So, where to now? Is there a way to actually test the resulting binaries as they are? Try a newer WiX version and see where it bombs? Upload the build result somewhere for you to check it? Cheers, -K.
smime.p7s
Description: S/MIME Cryptographic Signature
