Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.development.apps > #784
| From | Lew Pitcher <lew.pitcher@digitalfreehold.ca> |
|---|---|
| Subject | Re: How do I configure Autotools files for libexec installs? |
| Newsgroups | comp.os.linux.development.apps |
| References | <RZGax.14329$FK.8477@fx13.iad> <wwvzj4khddw.fsf@l1AntVDjLrnP7Td3DQJ8ynzIq3lJMueXf87AxnpFoA.invalid> |
| Organization | The Pitcher Digital Freehold |
| Message-ID | <WWHax.15823$d96.14593@fx21.iad> (permalink) |
| Date | 2015-05-31 13:56 -0400 |
On Sunday May 31 2015 13:20, in comp.os.linux.development.apps, "Richard
Kettlewell" <rjk@greenend.org.uk> wrote:
> Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:
> [...]
>> but none have resulted in a Makefile that would actually install the
>> file into the intended directory. Usually the @libexec@ just expands
>> into a literal '${exec_prefix}/libexec' path, without expanding the
>> ${exec_prefix}. Even the explicit '${exec_prefix}/libexec' just
>> "expands" into '${prefix}/libexec', still leaving the path unusable.
>
> You need definitions for exec_prefix and prefix as well. Example:
>
> $ cat configure.ac
> AC_INIT([whatever], [0.0], [whatever@example.com])
> AC_CONFIG_FILES([Makefile])
> AC_OUTPUT
> $ cat Makefile.in
> prefix=@prefix@
> exec_prefix=@exec_prefix@
> libbexecdir=@libexecdir@
> $ autoconf
> $ ./configure
> configure: creating ./config.status
> config.status: creating Makefile
> $ cat Makefile
> prefix=/usr/local
> exec_prefix=${prefix}
> libbexecdir=${exec_prefix}/libexec
>
> The idea is that setting just prefix is enough to redirect everything
> else.
That's got it. Thanks.
I tried it, and get the results I hoped for.
I guess that, for the other Makefile.in files, I'll have to do something
similar. Do you know of a guide to the expansion rules for the standard
macros (eg. @libexecdir@ -> @exec_prefix@/libexec, @exec_prefix@ -> @prefix@,
etc.)? I guess that I dig through config.log for the expansions, and
retro-fit them into my Makefile.in, if necessary.
--
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request
Back to comp.os.linux.development.apps | Previous | Next — Previous in thread | Find similar
How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 12:50 -0400
Re: How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 12:55 -0400
Re: How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 13:12 -0400
Re: How do I configure Autotools files for libexec installs? Richard Kettlewell <rjk@greenend.org.uk> - 2015-05-31 18:20 +0100
Re: How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 13:31 -0400
Re: How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 13:32 -0400
Re: How do I configure Autotools files for libexec installs? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-05-31 13:56 -0400
csiph-web