Hi All, In BlueZ, we are implementing a mesh.conf file, similar to the main.conf file already in use for the Bluetooth daemon. This will also be an issue with the main daemon once we start changing it over to using ELL as well. Our conf files are farely simple Key+Value files like this: ============== [General] # Comments Name = BlueZ AlwaysPairable = false PairableTimeout = 0 [GATT] ExchangeMTU = 517 ============== For this we want to include ell/settings.[ch] into our build, which performs this simple parsing. However, settings.c is currently including ell/pem-private.h, and has a link reference to pem_next(), via an extension mechanism. The PEM module then requires inclusion of cert, key, pkcs5 and base64. Is there a way to make this pem more "optional"? Because we have gone from a fairly simple inclusion of settings.c and it's header to needing to including the following modules, which is defeating part of the purpose of keeping ELL lean and mean: ell/settings.c ell/pem.c ell/cert.c ell/key.c ell/pkcs5.c ell/base64.c ell/settings.h ell/pem.h ell/pem-private.h ell/asn1-private.h ell/base64.h ell/cert.h ell/cert-private.h ell/key.h ell/pkcs5.h ell/pkcs5-private.h As far as I can tell, we do not use or need pem, cert, key, pkcs5, or base64 --Brian