Hi, I always wondered why it was not possible to have plugins in festival instead of recompiling the whole festival stuff each times a modification is done to a module.
Anyone could say that modules, and especially c coded part of them should contain enough stable things that should not be modified every morning. Anyway I noticed that it may be a problem to distribute adaptations such as specific languages modules if installation involves a compilation step. Certain users do not want to go into a compilation process. I realized that it does not seem a very difficult work to make festival accept plugins. The two attatched small files do the work. A module called festplugin simply export in the scheme world a method that allows to load a plugin. The init method in the plugin should return a LISP object that will allow to control the plugin once it is loaded. In the second archive there is a config.mak file that should be include in the festival config file. There are essentially two things : 1. linking festival against the dl library 2. adding the -E option at the festival linking step to expose festival symbols to the plugin. The latter looks the most problematic to me. It is certainly not a good practice to expose all festival symbols to the plugin and a suitable list should certainly be established. I am currently using this strategy on my own system and it looks prety good. I don't know if my code could be merged in a future festival release or at least integrated in the svn development archive. Moreover I'd be very sorry if the job had already been done and if I had miss something. Regards Pierre
config.tar.bz2
Description: Binary data
festplugin.tar.bz2
Description: Binary data
_______________________________________________ Festlang-talk mailing list [email protected] https://lists.berlios.de/mailman/listinfo/festlang-talk
