Rockbox mail archive

• Next message: Linus Nielsen Feltzing: "Re: plugins as multiple source files"
• Previous message: Daniel Stenberg: "Re: New Atmel remote control available"
• Next in thread: Linus Nielsen Feltzing: "Re: plugins as multiple source files"
• Reply: Linus Nielsen Feltzing: "Re: plugins as multiple source files"
• Reply: Mike Holden: "Re: plugins as multiple source files"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi

The current limitation that plugins must be a single source file is not a
really technical limitation, it is only the way the current build system
works. Since we are now seeing several plugins that share code, we should try
to solve this by allowing a single plugin get linked together from several
object/source files.

Anyone with a suggestion on how that would be best laid out in the file
system? Perhaps a single dir for each plugin (and each plugin dir would have a
Makefile that could specify additional object files to use), and then a
special dir with "plugin-libs" for generic code for multiple plugins to use?

Or how should we proceed to avoid code duplication in multiple source files?

-- 
 Daniel Stenberg -- http://rockbox.haxx.se/ -- http://daniel.haxx.se/
_______________________________________________
http://cool.haxx.se/mailman/listinfo/rockbox

• Next message: Linus Nielsen Feltzing: "Re: plugins as multiple source files"
• Previous message: Daniel Stenberg: "Re: New Atmel remote control available"
• Next in thread: Linus Nielsen Feltzing: "Re: plugins as multiple source files"
• Reply: Linus Nielsen Feltzing: "Re: plugins as multiple source files"
• Reply: Mike Holden: "Re: plugins as multiple source files"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]