Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.development.apps > #782

Re: How do I configure Autotools files for libexec installs?

Show all headers | View raw

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.
> 
> You mentioned Automake, which normally sorts thist stuff out for you,
> but I guess you’re not actually using it.


I tried automake, but the use documentation was even more spotty than
autoconf's documentation. For instance, the "Autotools book" discusses the
automake "Easy Primaries", which seem to include high-level rules for
compilation and installation of programs into <somepath>/bin , the
compilation and installation of libraries into <somepath>/bin and for the
movement of manual pages into <somepath>/man. But is says nothing else. And
the rest of the documentation regarding automake says even less.

The info page for these tools talks a lot about how they work, but not how to
use them. And the man page just points to the info page.

So, I abandon automake as complicating the issue, and just concentrate on
autoconf for now.


-- 
Lew Pitcher
"In Skills, We Trust"
PGP public key available upon request

Back to comp.os.linux.development.apps | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

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