Hi again,
answering to myself... I searched ChangeLog and found this:
2008-09-20 Ralf Wildenhues <ralf.wildenh...@gmx.de>
Remove unneeded per-rule *INSTALL variables.
* NEWS: Update.
* lib/am/data.am (%DIR%%PRIMARY%_INSTALL): Remove.
(install-%DIR%%PRIMARY%): Adjust.
* lib/am/libs.am (%DIR%LIBRARIES_INSTALL): Remove.
(install-%DIR%LIBRARIES): Adjust.
* lib/am/ltlibs.am (%DIR%LTLIBRARIES_INSTALL): Remove.
(install-%DIR%LTLIBRARIES): Adjust.
* lib/am/progs.am (%DIR%PROGRAMS_INSTALL): Remove.
(install-%DIR%PROGRAMS): Adjust.
[...]
It is explained in the NEWS:
Further, most undocumented per-rule install command variables such as
binSCRIPT_INSTALL have been removed because they are not needed any
more. Packages which use them should be using the appropriate one of
INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
counterpart, depending on the type of files and the need for automatic
target directory creation.
Indeed, setting "INSTALL_PROGRAM += @MY_AC_OPTIONS@" seems to do the trick.
But I have to split files according to install options :-(
Ale
On Sat 19/Jul/2014 20:47:53 +0200 I wrote:
> Hi,
> searching the web I found suggestions to use install-exec-hook and
> from there issue chown/chmod as needed. However, some years ago I had
> found instructions for setting those in Makefile.am like so:
>
> helloexecdir = @MY_AC_STUFF@
> helloexec_PROGRAMS = whatever
> helloexecPROGRAMS_INSTALL = $(INSTALL_PROGRAM)@MY_OTHER_AC_STUFF@
>
> First line still works, third one does not. MY_OTHER_AC_STUFF
> contains the required -o and -g options to install; the variable is
> defined but not used.
>
> Is that possibility gone for good? Are hooks the only way?
>
> TIA
> Ale
>
> P.S. I'm using automake 1.11.6 (Debian wheezy)
>
