Hi Sorry for me not reading that carefully, but i don't see how this is similar to libfprint issue. yes, the configure.in would look much cleaner and I agree that this is the way to go, but as I checked the other makefiles quickly I couldn't find any other advantages. Totem uses some kind of runtime module loading whereas AFAIK libfprint does that at compile-time, plus the "unwanted" code using ImageMagick is located in imgdev.c which is a part of the libfprint "core". You would need to put that into the drivers using it (currently only AES4000, as i remember) instead of general image driver for your plugin loading scheme to work as desired, that is removing the ImageMagick dependency for most users
I will add the other drivers and change the configure.in style and post it again soon, if you won't suggest a different approach. Pavel Bastien Nocera wrote: > See a prior mail on this very same mailing-list. It should be possible > to use something similar to Totem's configure.in to list the plugins you > want to install, and check their dependencies without turning the code > into spaghetti. > > _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
