Next: , Previous: , Up: The Macros  


ax_define_sub_path

Synopsis

AX_DEFINE_SUB_PATH(DEFNAME, varname, description)

Description

Look at varname and detect the subpath that it contains relative to $prefix/$exec_prefix. If the path is indeed relative to $prefix/$exec_prefix, then a single "./" (dotslash) is prepended, otherwise it can be seen as an absolute path that cannot be moved, which you possibly do for "/etc" files, or even those ending up in "/lib/modules" or "/winnt/system".

This macro is not very intelligent, it’s just a first try in this direction. It does currently just look into the current patterns, and replaces a ${prefix} with a simple dot. Amazingly, it works quite well for most packages.

Example (configure.ac):

  AX_DEFINE_DIR([EPREFIX], [exec_prefix], [--exec-prefix or default])
  AX_DEFINE_SUB_PATH([PATH_LIBDIR], [libdir], [--bindir subdir])
  AC_DEFINE_UNQUOTED([PACKAGE],"$PACKAGE", [Name of package])

Example (in C):

  static const char _libdir[] = PATH_LIBDIR; /* configure default */
  char* libdir;
  char* eprefix = getenv (PACKAGE "DIR");
  if (! eprefix) eprefix = EPREFIX; /* default */
  if (*_libdir != '.') libdir = strdup(_libdir);
  else {
     libdir = malloc(strlen(eprefix) + strlen(_libdir) + 2);
     strcpy(libdir, eprefix);
     strcat(libdir, PATH_DELIMITER_STRING);
     strcat(libdir, _libdir);
  }
  ...
  free (libdir);

The AX_DEFINE_SUB_PATHS(varnames) macro looks for the given various install-paths that largely depend on either ${prefix} or ${exec_prefix}. Just cut out the prefix and ac_define the value. The value is uppercased and PATH_ prepended ie. ax_define_sub_paths(bindir libdir pkgdatadir) will create the defines PATH_BINDIR PATH_LIBDIR PATH_PKGDATADIR - see posix’ include/paths.h that creates _PATH_DEV and friends.

Source Code

Download the latest version of ax_define_sub_path.m4 or browse the macro’s revision history.

License

Copyright © 2008 Guido U. Draheim guidod@gmx.de

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.

As a special exception, the respective Autoconf Macro’s copyright owner gives unlimited permission to copy, distribute and modify the configure scripts that are the output of Autoconf when processing the Macro. You need not follow the terms of the GNU General Public License when using or distributing such scripts, even though portions of the text of the Macro appear in them. The GNU General Public License (GPL) does govern all other use of the material that constitutes the Autoconf Macro.

This special exception to the GPL applies to versions of the Autoconf Macro released by the Autoconf Archive. When you make and distribute a modified version of the Autoconf Macro, you may extend this special exception to the GPL to apply to your modified version as well.


Next: , Previous: , Up: The Macros