On Fri, Oct 05, 2007 at 02:00:15AM +0200, Alon Bar-Lev wrote: > During my PKCS#11 work, I found that I can first help in cleaning > up the build system. > > I hope you accept this.
Everything looks pretty sane. Thanks for putting in the effort to clean up the build. > Rework the build environment so it will be more > flexible and maintainable. > > Major changes: > 1. The CFLAGS and LIBS of every library may be > specified to configure. > 2. Don't detect optional components, explicit --enable them. The distro's are all going to have to be in sync with this change. Right now eCryptfs will attempt to build every key module that it is possible to build by default; to keep that behavior, the --enable-* paramters will need to be added to spec files and what not. > 3. "make dist" works now as expected, and allow distribution to users. > 4. Generate documents for packager. > > Use "autoreconf -i -v -f" to generate autoconf/automake environment. But > before you do so, you must have dependencies' m4 files installed > (libgcrypt, gpgme, pkcs11-helper). I don't think ./configure should bomb out if PKCS11_HELPER_1_CHECK_FEATURES() is nowhere to be found. So far, I just have done a simple build/install/mount test with this patch set. I still need to set aside some time to take a closer look at the PKCS#11 module. As soon as I have a fix in the tree for the PKCS11_HELPER_1_CHECK_FEATURES() issue, I will make another release that includes these changes. Thanks, Mike
pgpmUr4ewzzZ5.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ eCryptfs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ecryptfs-devel
