Re: custom install targets

Scott Henry Harrison wrote:

> >> I would also like to be able to do things like:
> >> INSTALL_CUSTOM1 += file1
> >> INSTALL_CUSTOM1 += file2
> >> CUSTOM1DIR = /opt/lib/newlang/spec/
> > It would not be impossible to add something like this, but it's not too
> > difficult to do this with existing mechanisms.  E.g.: 
> > 
> > 	install-local:
> > 	   :cp $INSTALL_CUSTOM1 $CUSTOM1DIR
> 
> But, is it correct to say that the uninstallation would not
> be as automatic as it would for uninstall-exec, etc? 

Right, you also need to manually do something for uninstalling then.
It's very similar:

	uninstall-local:
	   :del $CUSTOM1DIR/$*INSTALL_CUSTOM1

Thus you need to add four lines (two if you already have a -local
install dependency).

To make it simpler would require introducing a new mechanism, that
requires knowing about.  I'm not sure if this is worth the effort.  I
would think that in most situations it's sufficient to use the default
INSTALL_ targets.  You can often use $INSTALL_DATA and set $DATADIR to
where the files are to be installed.  Perhaps one exception is when you
have several sub-directories, and the directory layout before installing
is different.

-- 
Linux is just like a wigwam: no Windows, no Gates and an Apache inside.

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///        Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html