[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: making a package install in a nonconventional dir

From: Alexandre Duret-Lutz
Subject: Re: making a package install in a nonconventional dir
Date: Thu, 07 Nov 2002 12:46:01 +0100
User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-debian-linux-gnu)

>>> "miki" == miki shapiro <address@hidden> writes:


 miki> How do I kindly ask automake (in to install
 miki> mypackage_PROGRAMS, mypackage_LIBRARIES, et cetra - into one directory -
 miki> /opt/mypackage for instance

mypackagedir = /opt/mypackage

It's probably best that you use bin_PROGRAMS, lib_PROGRAMS, or
similar standard directories, and let the user relocate these
directory where (s)he wants using 
  ./configure --bindir=/opt/mypackage --libdir=/opt/mypackage ...

Not everybody has/wants `/opt' on his system.

Here is the doc about the custom *dir variables:

|    Sometimes the standard directories--even as augmented by Automake--
| are not enough.  In particular it is sometimes useful, for clarity, to
| install objects in a subdirectory of some predefined directory.  To this
| end, Automake allows you to extend the list of possible installation
| directories.  A given prefix (e.g. `zar') is valid if a variable of the
| same name with `dir' appended is defined (e.g. `zardir').
|    For instance, until HTML support is part of Automake, you could use
| this to install raw HTML documentation:
|      htmldir = $(prefix)/html
|      html_DATA = automake.html
Alexandre Duret-Lutz

reply via email to

[Prev in Thread] Current Thread [Next in Thread]