Compilation of both SambaManger and Samba should cause no problems. All defaults have been set for the NEXTSTEP architecture (which should be fine for OPENSTEP too). All paths contain the default of /usr/local/samba or netinfo. The use of NetInfo has been enabled and the arch flags for all architectures have been set.
The only files which need modificatons are the ni_crypt.c in this directory and in samba-1.9.17p4/source/netinfo.
You should start with a `make' in the Samba distribution, then copy all binaries (nmbd nmblookup smbclient smbd smbpasswd smbrun smbstatus testparm testprns) and shell scripts (addtosmbpass smbtar *.sh) to SambaManager and then compile SambaManager (PB or `make'). This is because the Makefile in SambaManger expects to find the binaries when compiling the executable. The Samba tools are part of the SambaManager project.
One exception is the smbpasswd.file. This is *not* generated when compiling the Samba tools. This is only necessary if you do not wish to store the Samba passwords in NetInfo. In this case, remove the -DUSE_NETINFO in the Samba Makefile and the smbpasswd.o and recompile. Rename the smbpasswd to smbpasswd.file and move that to the SambaManger folder. If you will store the Samba passwords in NetInfo, you can create a dummy executable (empty file with x bits set will do) or link smbpasswd to smbpasswd.file.
VERY IMPORTANT
==============
The additional encryption and decryption routines are left blank. If you will store the Samba passwords in NetInfo, make sure to provide some good code for these routines, or you will risk making your passwords publically available! The routines are found in netinfo/ni_crypt.c.
