pth-config(1) [suse man page]

PTH-CONFIG(1)						       GNU Portable Threads						     PTH-CONFIG(1)

NAME

       pth-config - Pth library build utility

VERSION

       GNU Pth 2.0.7 (08-Jun-2006)

SYNOPSIS

       pth-config [--help] [--version] [--all] [--prefix] [--exec-prefix] [--bindir] [--libdir] [--includedir] [--mandir] [--datadir] [--acdir]
       [--cflags] [--ldflags] [--libs]

DESCRIPTION

       The pth-config program is a little helper utility for easy configuring and building applications based on the pth(3) library.  It can be
       used to query the C compiler and linker flags which are required to correctly compile and link the application against the pth(3) library.

OPTIONS

       pth-config accepts the following options:

       --help
	   Prints the short usage information.

       --version
	   Prints the version number and date of the installed pth(3) library.

       --all
	   Forces the output of all flags, that is, including extra flags which are not Pth specific.

       --prefix
	   Prints the installation prefix of architecture independent files

       --exec-prefix
	   Prints the installation prefix of architecture dependent files.

       --bindir
	   Prints the installation directory of binaries.

       --libdir
	   Prints the installation directory of libraries.

       --includedir
	   Prints the installation directory of include headers.

       --mandir
	   Prints the installation directory of manual pages.

       --datadir
	   Prints the installation directory of shared data.

       --acdir
	   Prints the installation directory of autoconf data.

       --cflags
	   Prints the C compiler flags which are needed to compile the pth(3)-based application. The output is usually added to the "CFLAGS" vari-
	   able of the applications "Makefile".

       --ldflags
	   Prints the linker flags ("-L") which are needed to link the application with the pth(3) library. The output is usually added to the
	   "LDFLAGS" variable of the applications "Makefile".

       --libs
	   Prints the library flags ("-l") which are needed to link the application with the pth(3) library. The output is usually added to the
	   "LIBS" variable of the applications "Makefile".

EXAMPLE

	CC	= cc
	CFLAGS	= -O `pth-config --cflags`
	LDFLAGS = `pth-config --ldflags`
	LIBS	= -lm `pth-config --libs`

	all: foo
	foo: foo.o
	    $(CC) $(LDFLAGS) -o foo foo.o $(LIBS)
	foo.o: foo.c
	    $(CC) $(CFLAGS) -c foo.c

SEE ALSO

       pth(3), cc(1).

AUTHOR

	Ralf S. Engelschall
	rse@engelschall.com
	www.engelschall.com

08-Jun-2006							   GNU Pth 2.0.7						     PTH-CONFIG(1)

Check Out this Related Man Page

NEON-CONFIG(1)							neon API reference						    NEON-CONFIG(1)

NAME

       neon-config - script providing information about installed copy of neon library

SYNOPSIS

       neon-config [--prefix] [[--cflags] | [--libs] | [--la-file] | [--support feature] | [--help] | [--version]]

DESCRIPTION

       The neon-config script provides information about an installed copy of the neon library. The --cflags and --libs options instruct how to
       compile and link an application against the library; the --version and --support options can help determine whether the library meets the
       applications requirements.

OPTIONS

       --cflags
	   Print the flags which should be passed to the C compiler when compiling object files, when the object files use neon header files.

       --libs
	   Print the flags which should be passed to the linker when linking an application which uses the neon library

       --la-file
	   Print the location of the libtool library script, libneon.la, which can be used to link against neon by applications using libtool.

       --version
	   Print the version of the library

       --prefix dir
	   If dir is given; relocate output of --cflags and --libs as if neon was installed in given prefix directory. Otherwise, print the
	   installation prefix of the library.

       --support feature
	   The script exits with success if feature is supported by the library.

       --help
	   Print help message; includes list of known features and whether they are supported or not.

EXAMPLE

       Below is a Makefile fragment which could be used to build an application against an installed neon library, when the neon-config script can
       be found in $PATH.

	   CFLAGS = `neon-config --cflags`
	   LIBS = `neon-config --libs`
	   OBJECTS = myapp.o
	   TARGET = myapp

	   $(TARGET): $(OBJECTS)
		$(CC) $(LDFLAGS) -o $(TARGET) $(OBJECTS) $(LIBS)

	   myapp.o: myapp.c
		$(CC) $(CFLAGS) -c myapp.c -o myapp.o

AUTHOR

       Joe Orton <neon@lists.manyfish.co.uk>
	   Author.

COPYRIGHT

neon 0.30.0							   31 July 2013 						    NEON-CONFIG(1)

Linux and UNIX Man Pages

pth-config(1) [suse man page]

Check Out this Related Man Page