From: Mathieu R. <mro...@en...> - 2005-01-03 17:46:28
|
When compiling xine for a tighter environment (for example, restrained diskspace and memory), it is useful to disable the compilation of unwanted plugins. I had to manually disable most plugins by going and modifying the makefiles. I, for one, would have appreciated if the configure scripts had allowed per-plugin exclusion. My two cents. Mat -----Original Message----- From: xin...@li... [mailto:xin...@li...] On Behalf Of Michael Roitzsch Sent: Monday, January 03, 2005 12:00 PM To: xin...@li... Cc: Alien; Andre Pang Subject: Re: [xine-devel] Put plugins in a plugins/ directory Hi, > > Why would anyone not want all plugins? I think its much easier for the > > users to have everything in one place. > > embedded systems? or a part of some other project that needs only a few > things, that way, that other project need not be dependant on some codec... Well, I can understand why someone would not want every plugin built and installed and I agree that we need a more powerful way to configure the xine-lib build, like adding configure options to enable/disable individual plugins. I even thought of a frontend to configure, maybe a shell script using 'dialog' to present something like the kernel config. But I still think the source should be one package. Michael -- printk(KERN_WARNING "Warning: defective CD-ROM (volume sequence number). Enabling \"cruft\" mount option.\n"); 2.2.16 /usr/src/linux/fs/isofs/inode.c ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ xine-devel mailing list xin...@li... https://lists.sourceforge.net/lists/listinfo/xine-devel |