Re: [vdr] change make install to be really useful
Quoting VDR User: > While we're on the topic of adjusting the Makefile.. I propose the > following change to install-plugins: > > old: > @cp --remove-destination $(PLUGINDIR)/lib/lib*-*.so.$(APIVERSION) > $(PLUGINLIBDIR) > > new: > @cp --remove-destination $(PLUGINDIR)/lib/*.$(APIVERSION) $(PLUGINLIBDIR) > > The difference is copying *.$(APIVERSION) rather then > lib*-*.so.$(APIVERSION). The reason is because not all plugins use > the same naming (softdevice for example) and this minor adjustment > would eliminate the need to edit the Makefile for this with every new > version of vdr, or having to manually copy them to the install dir. > Also I see no reason against it since we keep the APIVERSION. Which libs of softdevice are not matched by the "old" style ? Softdevice targets usually are: TARGETS = libvdr-$(PLUGIN).so and (with subplugins): TARGETS += lib$(PLUGIN)-xv.so TARGETS += lib$(PLUGIN)-dfb.so which are finally installed to: @cp $(CPOPTS) $@ $(LIBDIR)/[EMAIL PROTECTED](APIVERSION) And this should be match by : "lib*-*.so.$(APIVERSION)" > > And also the following change to clean-plugins: > > old: > @-rm -f $(PLUGINDIR)/lib/lib*-*.so.$(APIVERSION) > > new: > @-rm -f $(PLUGINDIR)/lib/*.$(APIVERSION) > @-rm -f $(PLUGINLIBDIR)/*.$(APIVERSION) > > Again using *.$(APIVERSION) instead of lib*-*.so.$(APIVERSION), and > also if we're going to clean plugins from the source dir, it seems > fitting to clean the installed ones as well since it's the expect > behavior from most users I've observed. > Stefan Lucke ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] change make install to be really useful
On Wed, 2007-08-15 at 18:55 +0200, Ludwig Nussel wrote: > Have a look at the SUSE vdr package. It installs headers and > Make.config into /usr/include/vdr. When compiling plugins you have > to use "make VDRDIR=/usr/include/vdr LIBDIR=/usr/lib/vdr all". it always strikes me, that vdrs build process is rather limiting. you can not just download a plugin unpack, build and install it. no, you have to first find your vdr source, unpack it to the right path, rename or link it correctly, then go to the vdr main dir and do make plugins, filling the screen with output of plugins you already compiled. most plugins even don't allow to be compiled from within its own root as they use the default Makefile. the way it should be IMHO is "make; make install" should build and install vdr (in $(PREFIX)/bin) and all plugins (in $(PREFIX)/lib/vdr) that are within PLUGINS/src/ and install vdrs headers in $(PREFIX)/include/vdr. additionally there should be a vdr.pc for plugins to use to get all needed info for building outside of vdrs source (most important CFLAGS). best regards ... clemens ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
