Re: OpenAFS for Windows - outstanding projects report and call for testers
Jeffrey Altman <[email protected]>
| Newsgroups | gmane.comp.file-systems.openafs.devel.win32 |
|---|---|
| Organization | No Longer Affiliated with Columbia University in the City of New York |
| Message-ID | <[email protected]> |
Chris Crowther wrote: > I can't even get it to compile for 2000/XP32 atm (which could be > down it being the pre-release version of .NET 2005). Right now it's > falling over on a redefinition of vsnprintf() - though looking at the > source it's only intended to be compiled on some UNIX varieties - I > just changed the #if definition to skip it if AFS_NT40_ENV is defined > (sorry I'm writing this at the same time as poking the source about). > > Some of the swithces have changed on .NET 2005 is about all I've > noticed so far (/GX is /EGsc for example) and a lot of warnings about > depreceated functions, but I'm guessing those have been there for a > while. I had to comment over a few of -WX switches as well to stop it > dying on depreciated functions, mostly sprintf(). > You will need to make new compiler version entries in config/NTMakefile.i386_nt40 if you are going to build with .NET 2005. I am not going to attempt to support that compiler until after the next major release. > If the compile for 2000/XP32 makes it through OK I shall try again > with the build enviroment for XP64. I'm assuming then that you do not have a 64-bit environment available to build / test. If you did, I would prefer a build using the .NET2003 compiler for 64-bit since that is what we will be shipping for the foreseeable future. > I take it you you know that nmake /f NTMakefile clean will fall > over if you run it before you've built anything? The > NTMakefile.version file doesn't exist in config/ so it gets a little > upset :) No, but its not surprising.
smime.p7s
(application/x-pkcs7-signature, 3.2 KB) - not displayed