configure should detect whatever it can by default should disable all default feature that are not available. This is how most [well behaved] configurations do.
But for sure disabling pcsc if openct is enabled is bad idea, as users may like them both and you start to add some of YOUR logic into the build process. I am not sure what you are trying to accomplish... people who build from sources should know what they are doing and are notified which options are enabled at configure summary. Distribution packages will use whatever they like and users will always have working environment. On Mon, Nov 2, 2009 at 3:56 PM, Ludovic Rousseau <ludovic.rouss...@gmail.com> wrote: > 2009/11/2 Alon Bar-Lev <alon.bar...@gmail.com>: >> You should follow the "detect" logic. >> Please follow openssl/zlib/iconv logic. > > I think "detect" is wrong. If pcsc-lite is not installed you will not > have a working configuration but you will not be warned either. > > If you want I can add code to disable pcsc if openct is used. So you > can continue to use "./configure --enable openct" as before. Would > that be a good idea? > > Bye > > -- > Dr. Ludovic Rousseau > _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel