views:

45

answers:

1

configure scripts always include something like the following in the help message:

...
By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc.  You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
  --bindir=DIR            user executables [EPREFIX/bin]
  --sbindir=DIR           system admin executables [EPREFIX/sbin]
  --libexecdir=DIR        program executables [EPREFIX/libexec]
  --sysconfdir=DIR        read-only single-machine data [PREFIX/etc]
  --sharedstatedir=DIR    modifiable architecture-independent data [PREFIX/com]
  --localstatedir=DIR     modifiable single-machine data [PREFIX/var]
  --libdir=DIR            object code libraries [EPREFIX/lib]
  --includedir=DIR        C header files [PREFIX/include]
  --oldincludedir=DIR     C header files for non-gcc [/usr/include]
  --datarootdir=DIR       read-only arch.-independent data root [PREFIX/share]
  --datadir=DIR           read-only architecture-independent data [DATAROOTDIR]
  --infodir=DIR           info documentation [DATAROOTDIR/info]
  --localedir=DIR         locale-dependent data [DATAROOTDIR/locale]
  --mandir=DIR            man documentation [DATAROOTDIR/man]
  --docdir=DIR            documentation root
                          [DATAROOTDIR/doc/gedit-line-ending-style-plugin]
  --htmldir=DIR           html documentation [DOCDIR]
  --dvidir=DIR            dvi documentation [DOCDIR]
  --pdfdir=DIR            pdf documentation [DOCDIR]
  --psdir=DIR             ps documentation [DOCDIR]

Program names:
  --program-prefix=PREFIX            prepend PREFIX to installed program names
...

What I would like to do is add "plugindir", to this section, as in:

...
  --dvidir=DIR            dvi documentation [DOCDIR]
  --pdfdir=DIR            pdf documentation [DOCDIR]
  --psdir=DIR             ps documentation [DOCDIR]
  --plugindir=DIR         Gedit plugin files [LIBDIR/gedit-2/plugins]
...

so that users would be able to pass in --plugindir=... to the configure script.

How can I do this?

A: 

If I'm correct those paths are set in the share/autoconf/autoconf/general.m4 file.

There are some examples that add a plugindir, for example in gstreamer, gimp and xine.

DiggyF
Interesting. Line 1058 of my `/usr/share/autoconf/autoconf/general.m4` file is responsible for the "Fine tuning of the installation directories:" line. It does not, however, appear that I can easily add to the "installation directories" section of the `configure` script help text without modifying `general.m4`. But, at least I now know.
Daniel Trebbien
Doesn't the gstreamer, or xine approach work for you?
DiggyF
@DiggyF: I am not sure which approach of gstreamer and xine you are referring to. But, what I did was adapted a line from `general.m4`, adding `AC_SUBST([plugindir], ['${libdir}/gedit-2/plugins'])` to my `configure.ac`. Then, I specify targets that I want to install to the "plugindir" in the `plugin_DATA` variable in a `Makefile.am`. It's not as user-configurable as I was originally going for, but it works well: http://code.google.com/p/gedit-line-ending-style-plugin/source/browse/trunk/src/Makefile.am
Daniel Trebbien