> A: Pete> No problems that I know with *building* but I didn't think it could be *installed* in Mac OS using 'configure && make install' as can be done with the Cyrus SASL. I think that would be a useful secondary goal for this piece of work.
Q: Pete> Which libraries?
-A:
-> Josh> the SASL library is self-contained within cyrus-sasl.
+>A: Josh> the SASL library is self-contained within cyrus-sasl.
> Sam> I think our changes have all been folded upstream at this point.
####Installer functionality:
There are two parts to the installation:
-1. The installer will install library and header files in /usr/local/lib and /usr/local/include, as for the Linux 'make install'.
+1: The installer will install library and header files in /usr/local/lib and /usr/local/include, as for the Linux 'make install'.
+
2: Frameworks: in addition, the installer will install frameworks in sub-directories of /Library/Frameworks on the main drive of the machine. The Cyrus SASL framework will be installed in /Library/Frameworks/SASL2.framework (as in the existing Cyrus SASL 'make install'). The Moonshot GSS EAP framework will be installed in /Library/Frameworks/MoonshotGSS_EAP.framework. The installer will create the .framework directories if they are not already present. The frameworks are wrappers for symlinks to the respective dynamic libraries in /usr/local/lib (libsasl2.dylib and mech_eap.dylib).
If an installation with a lower version number is present, the new installation will be installed, and the /Versions/Current alias changed to refer to the new installation.