[pclasses-devel] simplifying client-side integration of pclasses

[stephan b. <st...@s1...>]

Yo,

Attached is a script i would like to integrate into the configure 
process. It is a generator for PACKAGE_NAME-config scripts, best 
explained with an example:

PACKAGE_NAME=libpclasses \
  PACKAGE_VERSION=2004.12.x \
  prefix=$HOME \
  CLIENT_INCLUDES="-I${prefix}/include" \
  CLIENT_LDADD="-L${prefix}/lib -lpcore -lpio -lpsql -lpcrypto -lpnet" \
  ./PACKAGE_NAME-config.sh

That reads in PACKAGE_NAME-config.in (or $1, if it exists) and creates 
${PACKAGE_NAME}-config.

The generated script should be installed to PREFIX/bin and cleaned up 
during distclean.

stephan@owl:~/cvs/pclasses> ./libpclasses-config

./libpclasses-config: shows information useful for configuring/building 
libpclasses client applications.

Usage:
./libpclasses-config [options]

Options:
--libs        : prints linker information about what libs clients should 
link to
--includes    : prints INCLUDES information
--prefix      : prints the library's installation prefix
--version     : prints the library's version


Clients who build against pclasses can use this info to easily integrate 
the necessary INCLUDES and LDADD flags:

conf="$(which libpclasses-config)"
... if ! $conf then no pclasses ...
... else...
INCLUDES="$($conf --includes)"
LDADD="$($conf --libs)"



-- 
----- st...@s1...   http://s11n.net
"...pleasure is a grace and is not obedient to the commands
of the will." -- Alan W. Watts