jimzah/openafs
1
0
Fork 0
mirror of https://git.openafs.org/openafs.git synced 2025-02-01 14:07:39 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
openafs/src/WINNT/client_creds/NTMakefile

136 lines
3.2 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
# include the AFSD source tree on our inclusion path
afskfw-library-20040504 Migrate KFW functionality from src/WINNT/client_creds/afskfw* into a a new library to be shared by afslogon.dll, afscreds.exe Add KFW support to afslogon.dll ==================== 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. ==================== Migrate KFW functionality from src/WINNT/client_creds/afskfw* into a a new library to be shared by afslogon.dll, afscreds.exe Move IP Address Change Monitor into new source files. Add smbname support to the KFW set token functionality in afscreds.exe
2004-05-04 23:48:15 +00:00
AFSDEV_AUXCDEFINES = $(AFSDEV_AUXCDEFINES) /D"_AFXDLL" -I..\afsd -I..\client_config -I..\kfw\inc\krb5
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
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
# include the primary makefile
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
RELDIR=WINNT\client_creds
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
!INCLUDE ..\..\config\NTMakefile.$(SYS_NAME)
!INCLUDE ..\..\config\NTMakefile.version
############################################################################
#
# BUILD TARGETS
#
EXEFILE = $(DESTDIR)\root.client\usr\vice\etc\afscreds.exe
EXEOBJS = \
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
$(OUT)\advtab.obj \
$(OUT)\afswiz.obj \
$(OUT)\creds.obj \
$(OUT)\main.obj \
$(OUT)\misc.obj \
$(OUT)\credstab.obj \
$(OUT)\mounttab.obj \
$(OUT)\settings.obj \
$(OUT)\shortcut.obj \
$(OUT)\trayicon.obj \
$(OUT)\window.obj
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
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
EXECOBJS = \
afskfw-library-20040504 Migrate KFW functionality from src/WINNT/client_creds/afskfw* into a a new library to be shared by afslogon.dll, afscreds.exe Add KFW support to afslogon.dll ==================== 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. ==================== Migrate KFW functionality from src/WINNT/client_creds/afskfw* into a a new library to be shared by afslogon.dll, afscreds.exe Move IP Address Change Monitor into new source files. Add smbname support to the KFW set token functionality in afscreds.exe
2004-05-04 23:48:15 +00:00
$(OUT)\ipaddrchg.obj
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-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
EXERES = \
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
$(OUT)\afscreds_stub.res
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
AFSDOBJS = \
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
$(OUT)\fs_utils.obj
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
AFSAPPLIBOBJS= \
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
$(OUT)\checklist.obj \
$(OUT)\al_wizard.obj \
$(OUT)\subclass.obj
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
CLIENTOBJS = \
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
$(OUT)\drivemap.obj \
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
$(OUT)\RegistrySupport.obj
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
VCLIBS =\
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
iphlpapi.lib \
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
comctl32.lib \
shell32.lib \
uuid.lib \
ole32.lib \
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
mpr.lib \
netapi32.lib
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
EXELIBS = \
$(DESTDIR)\lib\afs\afspioctl.lib \
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
$(DESTDIR)\lib\libosi.lib \
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
$(DESTDIR)\lib\afs\TaLocale.lib \
ntmakefile-clean-20040401 Cleanup the *_component_version_number.* files in all directories
2004-04-01 20:29:38 +00:00
$(DESTDIR)\lib\lanahelper.lib \
$(DESTDIR)\lib\afsrxkad.lib \
afskfw-library-20040504 Migrate KFW functionality from src/WINNT/client_creds/afskfw* into a a new library to be shared by afslogon.dll, afscreds.exe Add KFW support to afslogon.dll ==================== 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. ==================== Migrate KFW functionality from src/WINNT/client_creds/afskfw* into a a new library to be shared by afslogon.dll, afscreds.exe Move IP Address Change Monitor into new source files. Add smbname support to the KFW set token functionality in afscreds.exe
2004-05-04 23:48:15 +00:00
$(DESTDIR)\lib\afsdes.lib \
$(DESTDIR)\lib\afsauthent.lib \
$(DESTDIR)\lib\libafsconf.lib \
$(DESTDIR)\lib\afskfw.lib
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
############################################################################
#
# EXTERNAL SOURCE FILES
#
# The following source files are required by this application, but live
# elsewhere in the tree. To prevent checking in more than one copy of the
# source files, they are copied to this directory at build-time.
#
COPYHEADERS = \
$(DESTDIR)\include\WINNT\al_wizard.h \
$(DESTDIR)\include\WINNT\checklist.h \
$(DESTDIR)\include\WINNT\subclass.h
############################################################################
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
AFSD = ..\afsd
AFSAPPLIB=..\afsapplib
CLIENT= ..\client_config
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
$(CLIENTOBJS): $(CLIENT)\$$(@B).cpp
$(C2OBJ) -I$*(*D) $**
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
$(AFSAPPLIBOBJS): $(AFSAPPLIB)\$$(@B).cpp
$(C2OBJ) -I$*(*D) $**
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
$(AFSDOBJS): $(AFSD)\$$(@B).c
$(C2OBJ) -I$*(*D) $**
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
$(EXEOBJS): $$(@B).cpp
$(C2OBJ) -I$*(*D) -I$(AFSAPPLIB) $**
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
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
$(EXECOBJS): $$(@B).c
$(C2OBJ) -I$*(*D) -I$(AFSAPPLIB) $**
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
############################################################################
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
$(EXEFILE) : $(EXEOBJS) $(EXECOBJS) $(EXERES) $(AFSAPPLIBOBJS) $(AFSDOBJS) $(CLIENTOBJS) $(EXELIBS)
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
$(EXEGUILINK) $(VCLIBS)
$(EXEPREP)
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 : $(COPYHEADERS) $(EXEFILE) lang
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
lang ::
$(CD) lang
for /f %l in ('dir /B ??_??') do @$(NTLANG) %l $(MAKECMD) /nologo /f NTMakefile install
$(CD) ..
############################################################################
#
# Dependencies
#
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
$(OUT)\afscreds_stub.res : afscreds_stub.rc AFS_component_version_number.h
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:
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
-mkdir $(OUT)\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
cd lang
nmake /nologo /f ntmakefile SRC=$(SRC) OBJ=$(OBJ) mkdir
cd ..
Initial IBM OpenAFS 1.0 tree
2000-11-04 02:13:13 +00:00
Reference in New Issue Copy Permalink