[vdr] [DISCUSSION REQUEST] reintroduce a common make configuration file in VDR-1.7.35

Manuel Reimer manuel.reimer at gmx.de
Wed Dec 26 15:54:46 CET 2012

Reinhard Nissl wrote:
> I understand that this seems to be a quite simple solution, because in the end,
> almost any other configuration option will be converted to either compiler or
> linker settings. But it's quite lowlevel and one has to dig through the Makefile
> in depth to extract the necessary compiler or linker options.

... so we have the same situation, we always had. You either have to find the 
configuration options in the Makefile or you have to find them somewhere in the 
documentation of the plugin, you want to build.

> I think that we should keep the possibility to configure highlevel plugin
> options from a central place like plugins.conf just as Make.config did up to
> VDR-1.7.33.

What is your plan? Do you want to build plugins "the old way" inside the VDR 
source dir? If so, then just add your options to your "Make.config" as you did 
in the past, but prefix them with an "export ". Something like:

export PLUGIN_OPTION = "any_value"

This way the options reach the plugin Makefiles if you do your "make plugins" as 
the global VDR Makefile exports the value.

If you don't plan to build all your plugins from the VDR source file, then a 
global configuration isn't needed. Then, the configuration should be part of the 
distribution specific package build scripts.



More information about the vdr mailing list