Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

neon-config(1) [centos 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)

Check Out this Related Man Page

NEON(3) 							neon API reference							   NEON(3)

NAME
neon - HTTP and WebDAV client library DESCRIPTION
neon is an HTTP and WebDAV client library. The major abstractions exposed are the HTTP session, created by ne_session_create(3); and the HTTP request, created by ne_request_create(3). HTTP authentication is handled transparently for server and proxy servers, see ne_set_server_auth(3); complete SSL/TLS support is also included, see ne_ssl_set_verify(3). CONVENTIONS
Some conventions are used throughout the neon API, to provide a consistent and simple interface; these are documented below. Thread-safeness and global initialization neon itself is implemented to be thread-safe (avoiding any use of global state), but in some configurations makes use of other libraries which require global initialization. The ne_sock_init(3) function should be called before any other use of the neon library interface. Namespaces The neon header files reserve the use of the prefixes ne_ and NE_. URI paths, WebDAV metadata The path strings passed to any function must be URI-encoded by the application: neon never performs any URI encoding or decoding automati- cally. WebDAV property names and values must be used un UTF-8. Memory handling neon does not attempt to cope gracefully with an out-of-memory situation; instead, by default, abort is called to terminate the applica- tion. Optionally an application-provided function be called before abort; see ne_oom_callback(3). Callbacks and userdata Whenever a callback is registered, a userdata variable is also used to allow the application to associate a context with the callback. The userdata is of type void *, allowing any pointer to be used. SEE ALSO
ne_session_create(3), ne_oom_callback(3) AUTHOR
Joe Orton <neon@webdav.org>. neon 0.23.5 8 October 2002 NEON(3)
Man Page