Re: defining xxx_PROGRAMS conditionally?
Did you mean autoconf 2.58? I don't see 2.59 anywhere... And where is CVS automake these days? Is it still on sourceware.cygnus.com? H -- Harlan == Harlan Stenn [EMAIL PROTECTED] writes: Harlan I know this has been discussed before, and I don't Harlan remember seeing a good solution. Perhaps this has Harlan changed with automake-1.7.7... It should be fixed in CVS Automake. Now that Autoconf 2.59 is out I'll try to prepare a first beta of Automake 1.8 soon (maybe this week-end). [...] -- Alexandre Duret-Lutz
Re: defining xxx_PROGRAMS conditionally?
Harlan == Harlan Stenn [EMAIL PROTECTED] writes: Harlan And where is CVS automake these days? Is it still on Harlan sourceware.cygnus.com? That machine was renamed to sources.redhat.com long ago. But yes, that is where it is hosted. Tom
defining xxx_PROGRAMS conditionally?
I know this has been discussed before, and I don't remember seeing a good solution. Perhaps this has changed with automake-1.7.7... I have a situation where I am using automake conditionals to control the installation directory of _PROGRAMS. In certain configurations I want them to be bin_PROGRAMS, and in others I want them to be bootbin_PROGRAMS. Sometimes automake-1.7.7 does not like this, and complains: utils/Makefile.am:30: automake does not support bin_PROGRAMS being defined conditionally utils/Makefile.am:42: automake does not support bootbin_PROGRAMS being defined conditionally I would rather not hack around this by always installing in bin_PROGRAMS and using the automake conditionals to override using: if FOO bindir=$(bootbindir) endif (assuming that would work...)_ What other solutions are there? One other strange thing - there are some directories where this same situation does not cause a complaint from automake, and so far I haven't been able to see the difference inhow I have specified things. H
Re: defining xxx_PROGRAMS conditionally?
Harlan == Harlan Stenn [EMAIL PROTECTED] writes: Harlan I know this has been discussed before, and I don't Harlan remember seeing a good solution. Perhaps this has Harlan changed with automake-1.7.7... It should be fixed in CVS Automake. Now that Autoconf 2.59 is out I'll try to prepare a first beta of Automake 1.8 soon (maybe this week-end). [...] -- Alexandre Duret-Lutz