Windows: Platform specific MIDL output Add $(CPU) to the MIDL generated _c.c and _s.c output files to prevent conflicts. Change-Id: Ie10c85fa0b9cab19b107b44c2cf452925b8ee521 Reviewed-on: http://gerrit.openafs.org/10907 Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com> Tested-by: Jeffrey Altman <jaltman@your-file-system.com>
Windows: remove trailing whitespace remove trailing whitespace from NTMakefile *.h *.c *.cpp *.idl *.def *.txt *.htm Change-Id: I948a7511a20d0ad522b647b788536f9b6f5dda16 Reviewed-on: http://gerrit.openafs.org/4548 Reviewed-by: Derrick Brashear <shadow@dementia.org> Tested-by: Derrick Brashear <shadow@dementia.org>
Windows: Permit build system to update symbol store Microsoft Debugging Tools for Windows, Visual Studio Debugger, and SysInternals tools can all make use of a Symbol Server. http://msdn.microsoft.com/en-us/magazine/cc163563.aspx The commit adds functionality to the build system to automatically add binaries and symbols to a symbol store during the build. This functionality is only enabled if two environment variables are defined: SYMSTORE_EXE - specifies the location of symstore.exe SYMSTORE_ROOT - specifies the location of the symbol store an optional environment variable permits an arbitrary comment to be added to the symbol store history file. SYMSTORE_COMMENT - arbitrary text to be added to the history LICENSE MIT Reviewed-on: http://gerrit.openafs.org/324 Reviewed-by: Jeffrey Altman <jaltman@openafs.org> Tested-by: Jeffrey Altman <jaltman@openafs.org>
windows-code-signing-20080702 LICENSE MIT Add code signing with signtool.exe to the build process. If all three of the required CODESIGN_xxxx environment variables are defined, signtool will be used to sign each exe, dll, and installer as they are built. The three environment variables are: CODESIGN_DESC = <description of application> CODESIGN_TIMESTAMP = <url of certificate authority timestamp server> CODESIGN_URL = <end user help URL> The default signing certificate is the one that will be used by signtool. If these environment variables are not defined, code signing will be skipped.
windows-no-more-rpcns4-dll-20080212 LICENSE MIT Remove all references to rpcns4.lib and its included functions RpcNsXXX. These APIs are no longer supported on Vista. Except for TaAfsAdmSvr they had been commented out for a long time but we still continued to link to the library. Loading the library generates a no longer supported error on Vista. So lets get rid of it.
windows-version-info-20070919 FIXES 71397 Many of the OpenAFS binaries that are installed on end user machines did not have version information. This is problematic as it is impossible to determine which version of a binary the crash report was filed against when a report is received by Microsoft Windows Error Reporting service.
windows-64-bit-type-safety-20051105 64-bit type safety changes required for successful compilation on Windows 64-bit systems with the VS 2005 compiler ==================== This delta was composed from multiple commits as part of the CVS->Git migration. The checkin message with each commit was inconsistent. The following are the additional commit messages. ==================== more corrections for use of 64-bit types on Windows ==================== 64-bit type safety changes required for successful compilation on Windows 64-bit systems with the VS 2005 compiler ==================== 64-bit type safety changes required for successful compilation on Windows 64-bit systems with the VS 2005 compiler ==================== 64-bit type safety changes required for successful compilation on Windows 64-bit systems with the VS 2005 compiler ==================== 64-bit type safety changes required for successful compilation on Windows 64-bit systems with the VS 2005 compiler ==================== 64-bit type safety changes required for successful compilation on Windows 64-bit systems with the VS 2005 compiler ==================== 64-bit type safety changes required for successful compilation on Windows 64-bit systems with the VS 2005 compiler ==================== 64-bit type safety changes required for successful compilation on Windows 64-bit systems with the VS 2005 compiler ==================== 64-bit type safety changes required for successful compilation on Windows 64-bit systems with the VS 2005 compiler
patch-from-shadow-to-jaltman-bkbox-20031120 This massive patch contains changes in several significant areas for Windows: - the ability to specify the mount point to be something other than /afs - functionality to assist debugging of the NT Services - support for languages other than English (NTLang.bat) - revisions to the Build system to support separate trees for src, obj, dest and free or checked; allow any MS compiler to be used - updates to NSIS installer build - mutex locking added to critical locations - updates to IS5 directory tree creation - update to afswsNetscape_config.sh
winnt-dotnet-support-20030812 "The 1.2.10 build ALMOST builds out of the box in Visual Studio .NET 2003. The MIDL compiler's default option changed from /NO_ROBUST to /ROBUST in version 6.0.359. So I propose that we put the /NO_ROBUST switch in the NTMakefiles as part of the command line."
windows-build-updates-20030314 support for V6.0 and .Net complier, compile from either NT4.0 or XP Source and object are separated into different directories. The directory tree would look as follows: Base from %AFSROOT% environment variable %AFSROOT%\src\... - all source and generated source %AFSROOT%\obj\checked\... objects from a checked build %AFSROOT%\obj\free\... objects from a free build %AFSROOT%\obj\dest\checked\... DEST folder from a checked build %AFSROOT%\obj\dest\free\.... DEST folder from a free build Before you start the build, you must build an object tree by issuing the following: nmake -f NTMAKEFILE mkdir ==================== This delta was composed from multiple commits as part of the CVS->Git migration. The checkin message with each commit was inconsistent. The following are the additional commit messages. ==================== support for V6.0 and .Net complier, compile from either NT4.0 or XP Source and object are separated into different directories. The directory tree would look as follows:
nt-makefile-clean-targets-20010917 more work on providing a clean target for nt
Standardize License information
Initial IBM OpenAFS 1.0 tree