jimzah/openafs
1
0
Fork 0
mirror of https://git.openafs.org/openafs.git synced 2025-01-21 08:20:16 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
53baa78733
openafs/src/NTMakefile

662 lines
12 KiB
Plaintext
Raw Normal View History

Standardize License information
2000-11-04 10:01:08 +00:00
# Copyright 2000, International Business Machines Corporation and others.
# All Rights Reserved.
#
# This software has been released under the terms of the IBM Public
# License. For details, see the LICENSE file in the top-level source
# directory or online at http://www.openafs.org/dl/license10.html
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
# Top level nmake NTMakefile driver for building AFS.
#
# This file simply imposes a reasonable total ordering on the set of
# directories to build; this ordering is of course more strict than the
# partial ordering established by the actual directory dependencies.
#
# When porting a new directory, simply add the directory into the
# dependence chain at the earliest point possible, updating its successor
# appropriately; if the new directory is the last in the chain, then
# update the 'finale' dependency to be the new directory.
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:
2003-03-14 20:11:44 +00:00
# These three macros define the source, object, and destination folders
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
2003-11-21 07:59:35 +00:00
SRC=$(AFSROOT)\src
windows-build-sys_name-20060214 Add the sys_name to the dest and obj directories in order to allow both 32-bit and 64-bit builds to be built from the same directory tree.
2006-02-14 14:03:17 +00:00
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:
2003-03-14 20:11:44 +00:00
#If AFS_OBJDIR is not defined then use obj as relative obj folder
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
2003-11-21 07:59:35 +00:00
!IFNDEF AFS_OBJDIR
windows-build-sys_name-20060214 Add the sys_name to the dest and obj directories in order to allow both 32-bit and 64-bit builds to be built from the same directory tree.
2006-02-14 14:03:17 +00:00
AFS_OBJDIR=$(AFSROOT)\obj\$(SYS_NAME)
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:
2003-03-14 20:11:44 +00:00
!ENDIF
windows-build-sys_name-20060214 Add the sys_name to the dest and obj directories in order to allow both 32-bit and 64-bit builds to be built from the same directory tree.
2006-02-14 14:03:17 +00:00
ntmakefile-reorder-20040618 place 'auth' before 'afsdobjs' to ensure creation of afs/cellconfig.h allow DESTDIR to be specified as an arbitrary location earlier in the build process.
2004-06-18 21:58:13 +01:00
!IFNDEF DESTDIR
windows-build-sys_name-20060214 Add the sys_name to the dest and obj directories in order to allow both 32-bit and 64-bit builds to be built from the same directory tree.
2006-02-14 14:03:17 +00:00
DESTDIR=$(AFSROOT)\dest\$(SYS_NAME)
ntmakefile-reorder-20040618 place 'auth' before 'afsdobjs' to ensure creation of afs/cellconfig.h allow DESTDIR to be specified as an arbitrary location earlier in the build process.
2004-06-18 21:58:13 +01:00
!ENDIF
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
CD = cd
windows-build-sys_name-20060214 Add the sys_name to the dest and obj directories in order to allow both 32-bit and 64-bit builds to be built from the same directory tree.
2006-02-14 14:03:17 +00:00
MKDIR = mkdir
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
NTMAKE = nmake /nologo /f ntmakefile install
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:
2003-03-14 20:11:44 +00:00
NTMAKELANG = nmake /nologo /f ntmakefile en_US
NTMAKE_HEADERS = nmake /nologo /f ntmakefile install_headers
windows-afsdb-and-freelance-afs-root-support-20011005 afsdb record support for windows freelance /afs (make up an afs root instead of using root.afs from some cell) support for windows
2001-10-05 23:40:44 +01:00
NTMAKE_OBJS = nmake /nologo /f ntmakefile install_objs
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
#debug statement support jumping to last know error
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
2003-11-21 07:59:35 +00:00
DOCD=$(SRC)\DOLASTCMP.BAT
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
config:
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\config
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\config
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
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:
2003-03-14 20:11:44 +00:00
procmgmt_headers:config
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\procmgmt
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\procmgmt
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE_HEADERS)
$(CD) ..\..
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:
2003-03-14 20:11:44 +00:00
afsreg_headers:
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\afsreg
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\afsreg
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE_HEADERS)
$(CD) ..\..\..
util: procmgmt_headers afsreg_headers
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
comerr: util
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
winnt-build-cleanup-20030825 include unified afs error support for winnt. removed dup'd code. supports building an installer with NSIS ==================== 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. ==================== include unified afs error support for winnt. removed dup'd code. supports building an installer with NSIS remove orphaned osi_malloc header ref ==================== more updates. make libadmin build, fix dependancies for unified_afs, copy rxstat header out during build ==================== fix NSIS installer build paths clean up base64 support for nt clean up int64 support in volser ==================== more updates. make libadmin build, fix dependancies for unified_afs, copy rxstat header out during build
2003-08-26 05:03:32 +01:00
afs: comerr
echo ***** $@
$(DOCD) $(SRC)\afs
$(CD) $(SRC)\afs
$(NTMAKE)
$(CD) ..\..
cmd: afs
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
afsreg: cmd
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
eventlog: afsreg
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
lwp: eventlog
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
rxgen: lwp
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
des: rxgen
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
death-to-des-stub-20060801 Remove des_stub; we don't care any more.
2006-08-01 22:19:53 +01:00
$(DOCD) $(SRC)\des
$(CD) $(SRC)\des
$(NTMAKE)
$(CD) ..\..
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
rx: des
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
windows-move-rxdebug-20070215 back in 2001 rxdebug was moved from src/rx to src/rxdebug for Unix but not for Windows. Move it for Windows as well.
2007-02-15 18:09:36 +00:00
rxdebug: rx
echo ***** $@
$(DOCD) $(SRC)\$@
$(CD) $(SRC)\$@
$(NTMAKE)
$(CD) ..\..
ubik_headers: rxdebug
ubik-call-sucks-20060704 make ubik_Call removal work on Windows. ==================== 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. ==================== another fix for Windows
2006-07-04 23:22:35 +01:00
echo ***** $@
$(DOCD) $(SRC)\ubik
$(CD) $(SRC)\ubik
$(NTMAKE_HEADERS)
$(CD) ..\..
rxstat: ubik_headers
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
rxkad: rxstat
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
pthread: rxkad
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
procmgmt: pthread
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
fsint: procmgmt
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
audit: fsint
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
osi_headers: audit
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\client_osi
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\client_osi
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE_HEADERS)
$(CD) ..\..\..
libacl_headers: osi_headers
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\libacl
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\libacl
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE_HEADERS)
$(CD) ..\..
cm_headers: libacl_headers
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\afsd
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\afsd
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE_HEADERS)
$(CD) ..\..\..
ntmakefile-auth-headers-20040618 break up auth build step into two parts to avoid circular dependency in the build process
2004-06-19 06:21:07 +01:00
auth_headers: cm_headers
ntmakefile-reorder-20040618 place 'auth' before 'afsdobjs' to ensure creation of afs/cellconfig.h allow DESTDIR to be specified as an arbitrary location earlier in the build process.
2004-06-18 21:58:13 +01:00
echo ***** $@
ntmakefile-auth-headers-20040618 break up auth build step into two parts to avoid circular dependency in the build process
2004-06-19 06:21:07 +01:00
$(DOCD) $(SRC)\auth
$(CD) $(SRC)\auth
$(NTMAKE_HEADERS)
ntmakefile-reorder-20040618 place 'auth' before 'afsdobjs' to ensure creation of afs/cellconfig.h allow DESTDIR to be specified as an arbitrary location earlier in the build process.
2004-06-18 21:58:13 +01:00
$(CD) ..\..
windows-toplevel-makefile-20050322 fix build dependencies for vl headers
2005-03-22 19:39:44 +00:00
vlserver_headers: auth_headers
echo ***** $@
$(DOCD) $(SRC)\vlserver
$(CD) $(SRC)\vlserver
$(NTMAKE_HEADERS)
$(CD) ..\..
afsdobjs: vlserver_headers
windows-afsdb-and-freelance-afs-root-support-20011005 afsdb record support for windows freelance /afs (make up an afs root instead of using root.afs from some cell) support for windows
2001-10-05 23:40:44 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\afsd
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\afsd
windows-afsdb-and-freelance-afs-root-support-20011005 afsdb record support for windows freelance /afs (make up an afs root instead of using root.afs from some cell) support for windows
2001-10-05 23:40:44 +01:00
$(NTMAKE_OBJS)
$(CD) ..\..\..
lanahelper-library-20040305 * at my request Asanka Hearth of MIT ripped out all of the code used the compute the Netbios Name of the SMB Server and the mountRoot and constructed one commonly used library called lanahelper.lib. This library is now constructed in the WINNT/afsd directory and used throughout the tree. At least we now have consistency if nothing else.
2004-03-05 23:09:18 +00:00
sys: afsdobjs
echo ***** $@
$(DOCD) $(SRC)\$@
$(CD) $(SRC)\$@
$(NTMAKE)
$(CD) ..\..
ntmakefile-auth-headers-20040618 break up auth build step into two parts to avoid circular dependency in the build process
2004-06-19 06:21:07 +01:00
auth: sys
echo ***** $@
$(DOCD) $(SRC)\$@
$(CD) $(SRC)\$@
$(NTMAKE)
$(CD) ..\..
ubik: auth
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
ptserver: ubik
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
libacl: ptserver
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
kauth: libacl
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
vlserver: kauth
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
usd: vlserver
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
bubasics: usd
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
budb: bubasics
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
butm: budb
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
$(NTMAKE)
$(CD) ..\..
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
dir: butm
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
vol: dir
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
volser: vol
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
viced: volser
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
update: viced
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
bucoord: update
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
$(NTMAKE)
$(CD) ..\..
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
butc: bucoord
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
$(NTMAKE)
$(CD) ..\..
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
bozo: butc
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
bosctlsvc: bozo
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
bu_utils: bosctlsvc
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
libafsrpc: bu_utils
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
libafsauthent: libafsrpc
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
tviced: libafsauthent
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
tbutc: tviced
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
$(NTMAKE)
$(CD) ..\..
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
libadmin: tbutc
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..
windows-install-updates-20010910 more corrections for windows packaging
2001-09-10 17:39:47 +01:00
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
adminutil: libadmin
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\libadmin\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\libadmin\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-install-updates-20010910 more corrections for windows packaging
2001-09-10 17:39:47 +01:00
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
vos: adminutil
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\libadmin\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\libadmin\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-install-updates-20010910 more corrections for windows packaging
2001-09-10 17:39:47 +01:00
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
client: vos
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\libadmin\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\libadmin\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-install-updates-20010910 more corrections for windows packaging
2001-09-10 17:39:47 +01:00
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
kas: client
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\libadmin\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\libadmin\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-install-updates-20010910 more corrections for windows packaging
2001-09-10 17:39:47 +01:00
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
pts: kas
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\libadmin\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\libadmin\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-install-updates-20010910 more corrections for windows packaging
2001-09-10 17:39:47 +01:00
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
bos: pts
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\libadmin\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\libadmin\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
cfg: bos
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\libadmin\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\libadmin\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
admintest: cfg
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\libadmin\test
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\libadmin\test
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
talocale: admintest
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
license: talocale
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
client_osi: license
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
afsd: client_osi
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
afsadmsvr: afsd
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
afsusrmgr: afsadmsvr
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
afssvrmgr: afsusrmgr
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
afssvrcfg: afssvrmgr
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
$(DOCD) $(SRC)\WINNT\$@
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
afssvrcpa: afssvrcfg
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
client_talocale: afssvrcpa
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
$(DOCD) $(SRC)\WINNT\talocale
$(CD) $(SRC)\WINNT\talocale
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
windows-makefile-20050509 reorganize dependencies to allow kfw to be integrated into Server Manager
2005-05-10 05:32:30 +01:00
client_cpa: client_talocale
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
client_config: client_cpa
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
client_exp: client_config
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
client_creds: client_exp
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\WINNT\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\WINNT\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
$(CD) ..\..\..
aklog-20040412 MIT's aklog.exe imported into the OpenAFS for Windows distribution ==================== 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. ==================== MIT's aklog.exe imported into OpenAFS for Windows
2004-04-13 05:06:17 +01:00
aklog: client_creds
echo ***** $@
$(DOCD) $(SRC)\WINNT\$@
$(CD) $(SRC)\WINNT\$@
$(NTMAKE)
$(CD) ..\..\..
windows-build-xstat-20071010 build xstat directory
2007-10-10 18:05:47 +01:00
xstat: aklog
echo ***** $@
$(DOCD) $(SRC)\$@
$(CD) $(SRC)\$@
$(NTMAKE)
$(CD) ..\..
netidmgr_plugin: xstat
windows-netidmgr-plugin-20061010 Secure Endpoints Inc. is contributing its AFS plug-in for KFW 3.1's Network Identity Manager to OpenAFS under an MIT style license.
2006-10-11 06:32:16 +01:00
echo ***** $@
$(DOCD) $(SRC)\WINNT\$@
$(CD) $(SRC)\WINNT\$@
$(NTMAKE)
$(CD) ..\..\..
extra: netidmgr_plugin
skyrope-mit-merge-hell-20040226 From Skyrope: The Skyrope work attempted to improve on the end user experience of using OpenAFS in the following ways: * Obtain tokens using renewable Kerberos 5 tickets in order to reduce the need for end users to renew expired tokens * Monitor the list of IP Addresses in order to detect changes in the network configuration which might affect the reachability of cells or the state of the AFS Client Service. When cells are newly reachable, obtain tokens for the cells. If the AFS Client Service is not running, start it. If tokens are expiring attempt to renew them. * Use KDC probes to detect the accessibility of realms/cells. If the KDC is not reachable, do not prompt the end user for a username and password. (fs probe is not implemented on windows) * Automatically obtain tokens using the Windows Logon Session Kerberos credentials (if available) * Allow tokens for multiple cells to be obtained by using the same Kerberos 5 tickets. (no UI yet implemented) * Perform drive mapping persistance by tracking it within the afsdsbmt.ini file instead of relying on the Windows Shell to persist the state. * Add new afscreds.exe command line options and change the default set used when creating the "AFS Credentials" shortcut in the Start Menu->Programs->Startup folder. From MIT: * Auto-detection of loopback adapters. Use "AFS" as the netbios name when a loopback adapter is installed. * Support for responding to power management events. Used to flush the cache when the machine is about to suspend, hibernate, or shutdown * Documentation of Registry entries * Support for Extended SMB Requests * Beginning of support for true Event Log reporting from a message database * Hidden Dot File support (configured via the HideDotFiles registry option) * Configurable Max number of Multiplexed Sessions (MaxMpxRequests registry option) * Configurable Max MTU size (RxMaxMTU registry option) * Configurable Jumbogram support (RxNoJumbo registry option) * Configurable Max number of Virtual Connections per Server (MaxVCPerServer registry option) * Win32 DNS API support * Addition of SMB_ATTR_xxxx defines for use instead of hex numbers * A variety of heap access and resource deallocation errors corrected in the SMB code * Support for recursive directory creation * Modifications to the en_US version of the client configuration dialog (need to port to other languages) Notes on the current check-in: * The KfW code will always be used when installed on the machine. This code only supports Krb5 and will not work with Krb4 only realms. A registry flag indicating whether or not KfW should be used if found needs to be added. * afscreds.exe needs to have a registry entry created to control the parameter list it should be started with. There should be a dialog to control this in the installer and within afscreds.exe * The MIT method of auto-assigning the mount-root and the netbios name is in conflict with the morgan stanley submissions in some parts of the code. If you are using the loopback adapter with this code both the "NetbiosName" = "AFS" and "Mountroot" = "/afs" registry options must be specified. This will be fixed in coming days.
2004-02-26 19:22:35 +00:00
! IF EXIST($(SRC)\WINNT\extra) && EXIST($(SRC)\WINNT\extra\NTMakefile)
echo ***** $@
$(DOCD) $(SRC)\WINNT\$@
$(CD) $(SRC)\WINNT\$@
$(NTMAKE)
$(CD) ..\..\..
! ELSE
echo ***** Skipping $@ ***** Not found.
! ENDIF
finale: extra
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
echo ***** $@
windows-more-updates-20030315 updates for build system
2003-03-15 15:08:30 +00:00
$(DOCD) $(SRC)\$@
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:
2003-03-14 20:11:44 +00:00
$(CD) $(SRC)\$@
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(NTMAKE)
windows-build-xstat-20071010 build xstat directory
2007-10-10 18:05:47 +01:00
$(CD) ..\..
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
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:
2003-03-14 20:11:44 +00:00
install: finale
windows-build-xstat-20071010 build xstat directory
2007-10-10 18:05:47 +01:00
echo Build Finished Successfully
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
win95-initial-port-20010430 Windows 95/98 port from IBM Almaden documentation and build support ==================== 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. ==================== Windows 95/98 port from IBM Almaden changes to cache manager ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden osi changes to support 95/98 ==================== Windows 95/98 port from IBM Almaden installer for 95/98 client ==================== Windows 95/98 port from IBM Almaden win95/98 panel app ==================== Windows 95/98 port from IBM Almaden win95/98 panel app help ==================== Windows 95/98 port from IBM Almaden makefile changes plus dns implementation ==================== Windows 95/98 port from IBM Almaden makefile changes plus changes for compat with dos line conventions ==================== Windows 95/98 port from IBM Almaden config for 95/98 ==================== Windows 95/98 port from IBM Almaden makefile changes plus support for 95/98 env ==================== Windows 95/98 port from IBM Almaden ms compiler changes ==================== Windows 95/98 port from IBM Almaden makefile changes ==================== Windows 95/98 port from IBM Almaden lwp changes to support 95/98 port ==================== Windows 95/98 port from IBM Almaden rx changes to support 95/98 port
2001-04-30 09:03:55 +01:00
# Clean target for obj tree
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:
2003-03-14 20:11:44 +00:00
clean:
windows-updates-20010108 "1. The default Open AFS is set to normal security (doesn't generate random user names). If you are installing over a previous version (before 1.2.2b) it's default is high security; therefore, if you want the normal security, you should uninstall the previous version (1.2.2a or earlier) and select to 'Not Preserve previous settings'. To manually change security you need to set the following registry keys: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemond\NetworkProvider LogonOptions = 1 - Integrated Logon LogonOptions = 2 - High Security options, Random User name generation LogonOptions = 3 - both 3. Windows 2000/NT, Win9x - First time installations will create necessary directories when user decides to download CellServDB 4. Windows 2000/NT, Global Drive working. 5. Windows XP - Drive mapping via GUI working. 6. Rename pthread.dll to afspthread.dll"
2002-01-08 20:44:31 +00:00
nmake /nologo /f ntmakefile "NTMAKE = nmake /nologo /f ntmakefile clean" "NTMAKE_HEADERS = nmake /nologo /f ntmakefile clean" "NTMAKE_OBJS = nmake /nologo /f ntmakefile clean" install
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:
2003-03-14 20:11:44 +00:00
nmake /nologo /f ntmakefile "NTMAKE = nmake /nologo /f ntmakefile clean" "NTMAKE_HEADERS = nmake /nologo /f ntmakefile clean" "NTMAKE_OBJS = nmake /nologo /f ntmakefile clean" media
$(CD) $(SRC)\config
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
nmake /nologo /f ntmakefile clean_version
$(CD) ..\..
# Language-only build target
lang:
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:
2003-03-14 20:11:44 +00:00
nmake /nologo /f ntmakefile "NTMAKE = nmake /nologo /f ntmakefile lang" "NTMAKE_HEADERS = nmake /nologo /f ntmakefile lang" install
mkdir:
ntmakefile-part-two-20040618 check in the correct version.
2004-06-18 22:08:50 +01:00
-mkdir $(AFS_OBJDIR)
-mkdir $(DESTDIR)
-mkdir $(AFS_OBJDIR)\checked
-mkdir $(AFS_OBJDIR)\free
death-to-des-stub-20060801 Remove des_stub; we don't care any more.
2006-08-01 22:19:53 +01:00
-xcopy /q /t /e $(SRC)\*.* $(AFS_OBJDIR)\checked\
-xcopy /q /t /e $(SRC)\*.* $(AFS_OBJDIR)\free\
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:
2003-03-14 20:11:44 +00:00
-mkdir $(DESTDIR)\checked
-mkdir $(DESTDIR)\free
-mkdir $(DESTDIR)\checked\bin
-mkdir $(DESTDIR)\free\bin
-@copy $(SRC)\config\NTLANG.BAT .
new-loopback-dll-20040622 Construct a new afsloopback.dll which contains the routines for installing, removing, and verifying the existance of a loopback adapter. This dll will be used by both the NSIS and the Wix installers. ==================== 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. ==================== Update the wix installer to use the new version of instloop.exe which uses the new afsloopback.dll
2004-06-23 09:48:18 +01:00
loopback:
echo ***** Making Loopback Adapter Utility DLL
$(DOCD) $(SRC)\WINNT\install\$@
$(CD) $(SRC)\WINNT\install\$@
$(NTMAKE)
$(CD) ..\..\..\..
loopback-20040623 properly set dependencies for NSIS and wix targets to build loopback target ==================== 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. ==================== do not install a second loopback adapter if one is already installed. ==================== 1. Custom actions should not depend on any library that is not in the Windows distribution. Change makefile to link with a static runtime. 2. Add common reporting mechanism to report ActionData messages back to the MSI process during the loopback installation. 3. CoInitializeSecurity can be called only once per process. When running as a custom action DLL under the MSI process we won't be able to successfully call this since the MSI process beats us to it. ==================== Compensate for difference in argument passing in MSI and RunDll32
2004-06-24 06:51:54 +01:00
NSIS: loopback
winnt-build-cleanup-20030825 include unified afs error support for winnt. removed dup'd code. supports building an installer with NSIS ==================== 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. ==================== include unified afs error support for winnt. removed dup'd code. supports building an installer with NSIS remove orphaned osi_malloc header ref ==================== more updates. make libadmin build, fix dependancies for unified_afs, copy rxstat header out during build ==================== fix NSIS installer build paths clean up base64 support for nt clean up int64 support in volser ==================== more updates. make libadmin build, fix dependancies for unified_afs, copy rxstat header out during build
2003-08-26 05:03:32 +01:00
echo ***** Making NSIS Installer
skyrope-mit-merge-hell-20040226 From Skyrope: The Skyrope work attempted to improve on the end user experience of using OpenAFS in the following ways: * Obtain tokens using renewable Kerberos 5 tickets in order to reduce the need for end users to renew expired tokens * Monitor the list of IP Addresses in order to detect changes in the network configuration which might affect the reachability of cells or the state of the AFS Client Service. When cells are newly reachable, obtain tokens for the cells. If the AFS Client Service is not running, start it. If tokens are expiring attempt to renew them. * Use KDC probes to detect the accessibility of realms/cells. If the KDC is not reachable, do not prompt the end user for a username and password. (fs probe is not implemented on windows) * Automatically obtain tokens using the Windows Logon Session Kerberos credentials (if available) * Allow tokens for multiple cells to be obtained by using the same Kerberos 5 tickets. (no UI yet implemented) * Perform drive mapping persistance by tracking it within the afsdsbmt.ini file instead of relying on the Windows Shell to persist the state. * Add new afscreds.exe command line options and change the default set used when creating the "AFS Credentials" shortcut in the Start Menu->Programs->Startup folder. From MIT: * Auto-detection of loopback adapters. Use "AFS" as the netbios name when a loopback adapter is installed. * Support for responding to power management events. Used to flush the cache when the machine is about to suspend, hibernate, or shutdown * Documentation of Registry entries * Support for Extended SMB Requests * Beginning of support for true Event Log reporting from a message database * Hidden Dot File support (configured via the HideDotFiles registry option) * Configurable Max number of Multiplexed Sessions (MaxMpxRequests registry option) * Configurable Max MTU size (RxMaxMTU registry option) * Configurable Jumbogram support (RxNoJumbo registry option) * Configurable Max number of Virtual Connections per Server (MaxVCPerServer registry option) * Win32 DNS API support * Addition of SMB_ATTR_xxxx defines for use instead of hex numbers * A variety of heap access and resource deallocation errors corrected in the SMB code * Support for recursive directory creation * Modifications to the en_US version of the client configuration dialog (need to port to other languages) Notes on the current check-in: * The KfW code will always be used when installed on the machine. This code only supports Krb5 and will not work with Krb4 only realms. A registry flag indicating whether or not KfW should be used if found needs to be added. * afscreds.exe needs to have a registry entry created to control the parameter list it should be started with. There should be a dialog to control this in the installer and within afscreds.exe * The MIT method of auto-assigning the mount-root and the netbios name is in conflict with the morgan stanley submissions in some parts of the code. If you are using the loopback adapter with this code both the "NetbiosName" = "AFS" and "Mountroot" = "/afs" registry options must be specified. This will be fixed in coming days.
2004-02-26 19:22:35 +00:00
$(DOCD) $(SRC)\WINNT\install\$@
$(CD) $(SRC)\WINNT\install\$@
winnt-build-cleanup-20030825 include unified afs error support for winnt. removed dup'd code. supports building an installer with NSIS ==================== 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. ==================== include unified afs error support for winnt. removed dup'd code. supports building an installer with NSIS remove orphaned osi_malloc header ref ==================== more updates. make libadmin build, fix dependancies for unified_afs, copy rxstat header out during build ==================== fix NSIS installer build paths clean up base64 support for nt clean up int64 support in volser ==================== more updates. make libadmin build, fix dependancies for unified_afs, copy rxstat header out during build
2003-08-26 05:03:32 +01:00
$(NTMAKE)
$(CD) ..\..\..\..
loopback-20040623 properly set dependencies for NSIS and wix targets to build loopback target ==================== 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. ==================== do not install a second loopback adapter if one is already installed. ==================== 1. Custom actions should not depend on any library that is not in the Windows distribution. Change makefile to link with a static runtime. 2. Add common reporting mechanism to report ActionData messages back to the MSI process during the loopback installation. 3. CoInitializeSecurity can be called only once per process. When running as a custom action DLL under the MSI process we won't be able to successfully call this since the MSI process beats us to it. ==================== Compensate for difference in argument passing in MSI and RunDll32
2004-06-24 06:51:54 +01:00
wix: loopback
msi-wix-installer-20040620 Update README-NT to include details on Wix MSI installer builder. Modify build system to create work directories and provide "wix" and "install-wix" build targets
2004-06-21 07:24:04 +01:00
echo ***** Making Wix MSI Installer
$(DOCD) $(SRC)\WINNT\install\$@
$(CD) $(SRC)\WINNT\install\$@
$(NTMAKE)
$(CD) ..\..\..\..
skyrope-mit-merge-hell-20040226 From Skyrope: The Skyrope work attempted to improve on the end user experience of using OpenAFS in the following ways: * Obtain tokens using renewable Kerberos 5 tickets in order to reduce the need for end users to renew expired tokens * Monitor the list of IP Addresses in order to detect changes in the network configuration which might affect the reachability of cells or the state of the AFS Client Service. When cells are newly reachable, obtain tokens for the cells. If the AFS Client Service is not running, start it. If tokens are expiring attempt to renew them. * Use KDC probes to detect the accessibility of realms/cells. If the KDC is not reachable, do not prompt the end user for a username and password. (fs probe is not implemented on windows) * Automatically obtain tokens using the Windows Logon Session Kerberos credentials (if available) * Allow tokens for multiple cells to be obtained by using the same Kerberos 5 tickets. (no UI yet implemented) * Perform drive mapping persistance by tracking it within the afsdsbmt.ini file instead of relying on the Windows Shell to persist the state. * Add new afscreds.exe command line options and change the default set used when creating the "AFS Credentials" shortcut in the Start Menu->Programs->Startup folder. From MIT: * Auto-detection of loopback adapters. Use "AFS" as the netbios name when a loopback adapter is installed. * Support for responding to power management events. Used to flush the cache when the machine is about to suspend, hibernate, or shutdown * Documentation of Registry entries * Support for Extended SMB Requests * Beginning of support for true Event Log reporting from a message database * Hidden Dot File support (configured via the HideDotFiles registry option) * Configurable Max number of Multiplexed Sessions (MaxMpxRequests registry option) * Configurable Max MTU size (RxMaxMTU registry option) * Configurable Jumbogram support (RxNoJumbo registry option) * Configurable Max number of Virtual Connections per Server (MaxVCPerServer registry option) * Win32 DNS API support * Addition of SMB_ATTR_xxxx defines for use instead of hex numbers * A variety of heap access and resource deallocation errors corrected in the SMB code * Support for recursive directory creation * Modifications to the en_US version of the client configuration dialog (need to port to other languages) Notes on the current check-in: * The KfW code will always be used when installed on the machine. This code only supports Krb5 and will not work with Krb4 only realms. A registry flag indicating whether or not KfW should be used if found needs to be added. * afscreds.exe needs to have a registry entry created to control the parameter list it should be started with. There should be a dialog to control this in the installer and within afscreds.exe * The MIT method of auto-assigning the mount-root and the netbios name is in conflict with the morgan stanley submissions in some parts of the code. If you are using the loopback adapter with this code both the "NetbiosName" = "AFS" and "Mountroot" = "/afs" registry options must be specified. This will be fixed in coming days.
2004-02-26 19:22:35 +00:00
windows-remove-is5-20070812 remove last trace of InstallShield5 from build rules
2007-08-13 04:11:55 +01:00
media: install NSIS wix
skyrope-mit-merge-hell-20040226 From Skyrope: The Skyrope work attempted to improve on the end user experience of using OpenAFS in the following ways: * Obtain tokens using renewable Kerberos 5 tickets in order to reduce the need for end users to renew expired tokens * Monitor the list of IP Addresses in order to detect changes in the network configuration which might affect the reachability of cells or the state of the AFS Client Service. When cells are newly reachable, obtain tokens for the cells. If the AFS Client Service is not running, start it. If tokens are expiring attempt to renew them. * Use KDC probes to detect the accessibility of realms/cells. If the KDC is not reachable, do not prompt the end user for a username and password. (fs probe is not implemented on windows) * Automatically obtain tokens using the Windows Logon Session Kerberos credentials (if available) * Allow tokens for multiple cells to be obtained by using the same Kerberos 5 tickets. (no UI yet implemented) * Perform drive mapping persistance by tracking it within the afsdsbmt.ini file instead of relying on the Windows Shell to persist the state. * Add new afscreds.exe command line options and change the default set used when creating the "AFS Credentials" shortcut in the Start Menu->Programs->Startup folder. From MIT: * Auto-detection of loopback adapters. Use "AFS" as the netbios name when a loopback adapter is installed. * Support for responding to power management events. Used to flush the cache when the machine is about to suspend, hibernate, or shutdown * Documentation of Registry entries * Support for Extended SMB Requests * Beginning of support for true Event Log reporting from a message database * Hidden Dot File support (configured via the HideDotFiles registry option) * Configurable Max number of Multiplexed Sessions (MaxMpxRequests registry option) * Configurable Max MTU size (RxMaxMTU registry option) * Configurable Jumbogram support (RxNoJumbo registry option) * Configurable Max number of Virtual Connections per Server (MaxVCPerServer registry option) * Win32 DNS API support * Addition of SMB_ATTR_xxxx defines for use instead of hex numbers * A variety of heap access and resource deallocation errors corrected in the SMB code * Support for recursive directory creation * Modifications to the en_US version of the client configuration dialog (need to port to other languages) Notes on the current check-in: * The KfW code will always be used when installed on the machine. This code only supports Krb5 and will not work with Krb4 only realms. A registry flag indicating whether or not KfW should be used if found needs to be added. * afscreds.exe needs to have a registry entry created to control the parameter list it should be started with. There should be a dialog to control this in the installer and within afscreds.exe * The MIT method of auto-assigning the mount-root and the netbios name is in conflict with the morgan stanley submissions in some parts of the code. If you are using the loopback adapter with this code both the "NetbiosName" = "AFS" and "Mountroot" = "/afs" registry options must be specified. This will be fixed in coming days.
2004-02-26 19:22:35 +00:00
loopback-20040623 properly set dependencies for NSIS and wix targets to build loopback target ==================== 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. ==================== do not install a second loopback adapter if one is already installed. ==================== 1. Custom actions should not depend on any library that is not in the Windows distribution. Change makefile to link with a static runtime. 2. Add common reporting mechanism to report ActionData messages back to the MSI process during the loopback installation. 3. CoInitializeSecurity can be called only once per process. When running as a custom action DLL under the MSI process we won't be able to successfully call this since the MSI process beats us to it. ==================== Compensate for difference in argument passing in MSI and RunDll32
2004-06-24 06:51:54 +01:00
install-nsis: install NSIS
nmake-convenience-20031210 Add new targets install-nsis and install-is5 to perform both a build and an installer in one shot
2003-12-11 03:57:56 +00:00
loopback-20040623 properly set dependencies for NSIS and wix targets to build loopback target ==================== 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. ==================== do not install a second loopback adapter if one is already installed. ==================== 1. Custom actions should not depend on any library that is not in the Windows distribution. Change makefile to link with a static runtime. 2. Add common reporting mechanism to report ActionData messages back to the MSI process during the loopback installation. 3. CoInitializeSecurity can be called only once per process. When running as a custom action DLL under the MSI process we won't be able to successfully call this since the MSI process beats us to it. ==================== Compensate for difference in argument passing in MSI and RunDll32
2004-06-24 06:51:54 +01:00
install-wix: install wix
skyrope-mit-merge-hell-20040226 From Skyrope: The Skyrope work attempted to improve on the end user experience of using OpenAFS in the following ways: * Obtain tokens using renewable Kerberos 5 tickets in order to reduce the need for end users to renew expired tokens * Monitor the list of IP Addresses in order to detect changes in the network configuration which might affect the reachability of cells or the state of the AFS Client Service. When cells are newly reachable, obtain tokens for the cells. If the AFS Client Service is not running, start it. If tokens are expiring attempt to renew them. * Use KDC probes to detect the accessibility of realms/cells. If the KDC is not reachable, do not prompt the end user for a username and password. (fs probe is not implemented on windows) * Automatically obtain tokens using the Windows Logon Session Kerberos credentials (if available) * Allow tokens for multiple cells to be obtained by using the same Kerberos 5 tickets. (no UI yet implemented) * Perform drive mapping persistance by tracking it within the afsdsbmt.ini file instead of relying on the Windows Shell to persist the state. * Add new afscreds.exe command line options and change the default set used when creating the "AFS Credentials" shortcut in the Start Menu->Programs->Startup folder. From MIT: * Auto-detection of loopback adapters. Use "AFS" as the netbios name when a loopback adapter is installed. * Support for responding to power management events. Used to flush the cache when the machine is about to suspend, hibernate, or shutdown * Documentation of Registry entries * Support for Extended SMB Requests * Beginning of support for true Event Log reporting from a message database * Hidden Dot File support (configured via the HideDotFiles registry option) * Configurable Max number of Multiplexed Sessions (MaxMpxRequests registry option) * Configurable Max MTU size (RxMaxMTU registry option) * Configurable Jumbogram support (RxNoJumbo registry option) * Configurable Max number of Virtual Connections per Server (MaxVCPerServer registry option) * Win32 DNS API support * Addition of SMB_ATTR_xxxx defines for use instead of hex numbers * A variety of heap access and resource deallocation errors corrected in the SMB code * Support for recursive directory creation * Modifications to the en_US version of the client configuration dialog (need to port to other languages) Notes on the current check-in: * The KfW code will always be used when installed on the machine. This code only supports Krb5 and will not work with Krb4 only realms. A registry flag indicating whether or not KfW should be used if found needs to be added. * afscreds.exe needs to have a registry entry created to control the parameter list it should be started with. There should be a dialog to control this in the installer and within afscreds.exe * The MIT method of auto-assigning the mount-root and the netbios name is in conflict with the morgan stanley submissions in some parts of the code. If you are using the loopback adapter with this code both the "NetbiosName" = "AFS" and "Mountroot" = "/afs" registry options must be specified. This will be fixed in coming days.
2004-02-26 19:22:35 +00:00
windows-remove-is5-20070812 remove last trace of InstallShield5 from build rules
2007-08-13 04:11:55 +01:00
Reference in New Issue Copy Permalink