[vdr] [DISCUSSION REQUEST] reintroduce a common make configuration file in VDR-1.7.35
Klaus.Schmidinger at tvdr.de
Thu Dec 27 17:11:17 CET 2012
On 26.12.2012 20:19, Udo Richter wrote:
> Oh, and by the way, with introducing $(CWD) some previously relative paths got hard coded, so moving these builds around or accessing them from different mount points might now be broken. For example, my default lib dir changed from ./PLUGINS/lib to /usr/src/pc/vdr/vdr-1.7.34/PLUGINS/lib, which only
> makes sense within a single virtual machine that cannot even run VDR at all. I'll have to add some overrides for that.
The attached patch changes the VDR Makefile back to using relative paths
if the plugins are built locally.
The patch also contains
- Making sure that plugins include the VDR header files from the actual VDR source
directory when doing "make plugins" (suggested by Christoper Reimer).
- Increased the version numbers of all plugins to reflect the recent Makefile changes.
- If set, DVBDIR is now conveyed to plugins via the CFLAGS.
- Removed some redundancy from Make.config.template.
- Changed "==" to "=" in the Makefile to make it POSIX style.
- Now using targets "install-lib" and "install-i18n" when building plugins locally.
- Added MANDIR to the vdr.pc file, so that plugins that need it can retrieve it via
MANDIR = $(DESTDIR)$(call PKGCFG,mandir).
- Using relative paths again when building plugins locally (by request of Udo Richter).
...still considering what to do with the plugin configuration stuff. Currently I tend to
put a "plgcfg" entry into vdr.pc, since apparently everybody wants this to be somewhere else.
I'm just glad Linux distribution managers don't build cars - otherwise we would most
likely be long dead before we find the brake pedal... ;-)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3043 bytes
Desc: not available
More information about the vdr