LICENSE MIT
Add code signing with signtool.exe to the build process.
If all three of the required CODESIGN_xxxx environment
variables are defined, signtool will be used to sign each
exe, dll, and installer as they are built.
The three environment variables are:
CODESIGN_DESC = <description of application>
CODESIGN_TIMESTAMP = <url of certificate authority timestamp server>
CODESIGN_URL = <end user help URL>
The default signing certificate is the one that will be used by
signtool. If these environment variables are not defined, code
signing will be skipped.
(cherry picked from commit 65bf7cdb6d20a1ff4e71c79347782aa3b5f1e3f8)
To prevent stripping, specify the '--disable-strip-binaries' option on
the ./configure command line. fileserver and volserver are never stripped.
When --enable-debug is specified, binaries will not be stripped by default.
When using the install-sh that ships with the source tree, Autoconf
substitutes in a relative path just to be annoying. Define the INSTALL
variables in each individual Makefile so that they find the proper file.
Remove the definitions from Makefile.config so that no one will
accidentally get the wrong ones.
Delete pinstall and convert the entire tree to use the install program
found by configure (falling back on install-sh in the local tree). This
means that we have to pre-create directories with install -d. Also redo
the install and dest rules to be lists of install rules rather than
dependencies driving separate make rules so that running make install will
always update the target directory with the current code, even if there are
files in the install area that are newer.
Stop installing libafssetpag; we're about to kill it in favor of a
different library. Remove some djgpp rules.
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
64-bit time_t pointer update
====================
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.
====================
correct a type for consistency
====================
corrections to the dafs delta to allow compilation on Windows
64-bit type safety changes required for successful compilation
on Windows 64-bit systems with the VS 2005 compiler
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
more corrections for use of 64-bit types on Windows
====================
64-bit type safety changes required for successful compilation
on Windows 64-bit systems with the VS 2005 compiler
====================
64-bit type safety changes required for successful compilation
on Windows 64-bit systems with the VS 2005 compiler
====================
64-bit type safety changes required for successful compilation
on Windows 64-bit systems with the VS 2005 compiler
====================
64-bit type safety changes required for successful compilation
on Windows 64-bit systems with the VS 2005 compiler
====================
64-bit type safety changes required for successful compilation
on Windows 64-bit systems with the VS 2005 compiler
====================
64-bit type safety changes required for successful compilation
on Windows 64-bit systems with the VS 2005 compiler
====================
64-bit type safety changes required for successful compilation
on Windows 64-bit systems with the VS 2005 compiler
====================
64-bit type safety changes required for successful compilation
on Windows 64-bit systems with the VS 2005 compiler
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
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:
"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"
according to jeff:
- Renames the top-level 'install' target to 'build'. This should be
transparent, since no one should be using that.
- Improves on Sam's dirpath patches, by splitting out server binaries
into separate bin, sbin, and libexec directories in GCS mode (these
are all /usr/afs/bin in Transarc mode).
- Updates the top-level 'all' target so that it builds the software
but does not generate a dest tree. Top-level 'lib' and 'include'
directories are generated to hold the intermediate libraries and headers
used during the build.
- Adds a new top-level 'install' target, which installs things in the
appropriate directories under ${DESTDIR}, based on configure's install
directories plus the extras added by Sam's patch.
- Adds a new top-level 'dest' target, which creates an old-style dest
directory under ${DEST}. The ${DEST} variable defaults to the
traditional value of ${SRCDIR_PARENT}/${SYS_NAME}/dest. Note that
this variable used to be called ${DESTDIR}; it was renamed to avoid
conflicts with the de facto standard usage of ${DESTDIR}.
====================
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.
====================
fix missed makefile
====================
update another missed file
====================
eliminate bogus escaping
====================
get rid of another bogus escape
====================
remove unused include directory
====================
get rid of no longer used libdir
====================
remove unused incdir
====================
fix up some problems for make compatibility and missing trailing /
====================
put afs.exp in the right place
====================
remove bogus afssrvdir reference
====================
update dest version of output
====================
update ref to libexecdir
====================
kill refs to afssrvdir
====================
convert missed LIBDIR to TOP_LIBDIR
====================
remove explicit INSTALL and use makefile.@sys value instead
====================
except it's helpful to actually include makefile.@sys
====================
convert LIBDIR to TOP_LIBDIR
get rid of cases where we'd end up with two / because of DESTDIR pasting
macroize calls to rm
====================
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.
====================
get rid of another case of bogus trailing quoting
clean up all the makefiles to remove bogus targets, eliminate trailing /
requirement from DESTDIR, avoid needing to pass things like DESTDIR around
between makefiles
====================
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.
====================
remove bogus quoting
1. Version control (Win9x & Windows NT/2000)
NTMakefile.i386_win95 and NTMakefile.i386_nt40 added AFSPRODUCT_VERSION
variable, setting this will propagate through the software by setting
the product version for the installation and client dialog boxes. In
particular it will provide correct notification if Win2K installation is
being upgraded, reinstall or downgraded.
Version information shows up in the following ways:
Welcome dialog during installation
Properities page for Install.exe (Windows Installation routine)
Windows Add/Remove Dialogs application list
AFS Control Center and Client dialog boxes
See README-WIN9X.TXT or README-NT.TXT for further information on how to set thi
s
variable.
2. CellServDB (Win9x & Windows NT/2000)
The installer can choose between various sources for CellServDB:
a) Previous installed file, afsdcell.ini(WinNT/2000) or CellServDB(Win9x).
b) File that comes with the installation package (recent copy from grand.centra
l.org)
c) Download a the file from the Web (default http://grand.central.org/dl/cellse
rvdb/CellServDB).
d) Browse for a file
3. Drive Mapping (Win9x & Windows NT/2000)
The installer can choose up to two drive mappings during the installation
process. Default is map Z: to AFS root and U: to user home directory
4. Silent Running (Win9x & Windows NT/2000)
Setup.exe is capable of running silently (-s option); that is, it will use a pr
e-made
response script to drive its responses. You can also do a normal installation
with
the record option (-r) to build a sample response file.
The installation routine has been improved to accept a modified response file s
o the
administrator can setup up additional drive mappings including substituting the
user's
loggin name into the path. By using a text editor an administrator can setup a
variable
path name that includes %LOGINNAME% in a path statement. This variable will be
substituted for the current user's login name. (Only at installation time.)
For example: if an administrator wanted to install AFS client on a machine that
had the
following mappings:
Z:=/
U:=/afs/afscell.org/u/username
Q:=/afs/afscell.org/general
Then follow these steps:
a) run setup with -r option and specify install to record responses into file s
etup.iss
setup.exe -r -f1setup.iss
b) Follow normal installation responses
c) Edit the setup.iss response file by modifying the "DRIVEPATH section".
This response file could start off looking like this:
[DLG_DRIVEPATH-1]
Result=1
Drive_0=Z:
Path_0=/
Share_0=all
Drive_1=U:
Path_1=/afs/afscell.org/u/administrator
Share_1=home
Count=2
This section map would be changed to look like this:
[DLG_DRIVEPATH-1]
Result=1
Drive_0=Z:
Path_0=/
Share_0=all
Drive_1=U:
Path_1=/afs/afscell.org/u/%LOGINNAME%
Share_1=home
Drive_2=Q:
Path_2=/afs/afscell.org/general
Share_2=genrl
Count=3
d) Use the silent mode to install AFS (must log to windows as your user name e.
g. Frank)
setup.exe -s -f1setup.iss
HINT: Share name should be limited to 12 characters.
The response file terminate if the installation is in any way different; for
example,
the response is recorded on a clean machine and it is run on a system where
AFS
is already installed.
The execution is truly silent, except for a log file.
The last response is BootOption and if set to 1 it will reboot your machine!
Refer to additional documentation on silent/record in you Install Shield User's
Guide.
5. Fixed the Un-Installation bug that damaged the NetBT parameter registration. (Win2k/NT only)
6. Change Default selection for Win2000 to Client and Documentation only. (Win2
K/NT only)
The default installation is with Server and Control Center NOT selected.
7. Win9x Client Operation (Win9x only)
Win9x client has been changed to allow "connection" with out forcing
authentication. Previous implementation of the Win9x client had three steps to
the
connection process: 1) start client 2) obtain tokens 3) Map drives
The updated Win9x client can leave the username blank and select to Connect. T
herefore, only
the client will be started (without obtaining tokens). The user can still map
drives
(those that don't require authentication). This is particularity useful if you
want to
use a different routine to obtain authentication tokens or additional drive map
pings.
A command line option has also been added (-noid). This option Prevent selecti
on of
(Gray out) username/password. This will cause the client to start up without au
thentication.
By using both -noid and -connect allows the user to run the AFS client in login
script
that could provide Kerbos 5 authentication and addition drive mapping.
8. Installation (Win9x only)
Fix installation into paths that have space, e.g. \Program Files\Afscli
====================
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.
====================
complete list in first message
setup for darwin port
====================
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.
====================
changes for darwin port
====================
added files for the darwin port
====================
changes for darwin port
