Next: , Previous: , Up: library.make   [Contents]


1.4.8.1 Project Variables

Library project: LIBRARY_NAME

LIBRARY_NAME should be assigned the list of name of libraries to be generated. Most UNIX systems expect that the filename for the library has the word lib prefixed to the name; i.e. the c library has filename of libc. Prefix the lib to the library name when it is specified in the LIBRARY_NAME variable because the Makefile Package will not automatically prefix it.

Library project: C_FILES

xxx_C_FILES is the list of C files, with a .c extension, that are to be compiled to generate the xxx library. Replace the xxx with the name of the library as listed by the LIBRARY_NAME variable.

Library project: OBJC_FILES

xxx_OBJC_FILES is the list of Objective-C files, with a .m extension, that are to be compiled to generate the xxx library. Replace the xxx with the name of the library as listed by the LIBRARY_NAME variable.

Library project: PSWRAP_FILES

xxx_PSWRAP_FILES is the list of PostScript wrap files, with a .psw extension, that are to be compiled to generate the xxx library. PostScript wrap files are processed by the pswrap utility which generates a .c and a .h file from each .psw file; the generate .c file is the file actually compiled. Replace the xxx with the name of the library as listed by the LIBRARY_NAME variable.

Library project: HEADER_FILES

xxx_HEADER_FILES is the list of header filenames that are to be installed with the library. If a filename has a directory path prefixed to it then that prefix will be maintained when the headers are installed. It is up to the user to make sure that the installation directory exists; otherwise, an error will occur when the library is installed, see xxx_HEADER_FILES_INSTALL_DIR. Replace the xxx with the name of the library as listed by the LIBRARY_NAME variable.

Library project: HEADER_FILES_DIR

xxx_HEADER_FILES_DIR is the relative path from the current directory, where the makefile is located, to where the header files specified by xxx_HEADER_FILES are located. If a filename specified in xxx_HEADER_FILES has a directory path prefixed to it then that path will not be removed when the Makefile Package accesses the files, so do not specify a path with xxx_HEADER_FILES_DIR that is already prefixed to the header filenames, see xxx_HEADER_FILES_INSTALL_DIR. xxx_HEADER_FILES_DIR is optional; leaving it blank or undefined, and the Makefile Package assumes that the relative path to the header files is the current directory where the makefile resides. Replace the xxx with the name of the library as listed by the LIBRARY_NAME variable.

Library project: HEADER_FILES_INSTALL_DIR

xxx_HEADER_FILES_INSTALL_DIR specifies the relative subdirectory path below GNUSTEP_HEADERS where the header files are to be installed. If this directory or any of its parent directories do not exist, then the Makefile Package will create them. The Makefile Package prefixes xxx_HEADER_FILES_INSTALL_DIR to each of the filenames in xxx_HEADER_FILES when they are installed, so if the filenames in xxx_HEADER_FILES already have a directory path prefixed then the user is responsible for creating that directory, the Makefile Package will not create. xxx_HEADER_FILES_INSTALL_DIR is optional; leaving it blank or undefined, and the Makefile Package assumes that the installation directory is just GNUSTEP_HEADERS with no subdirectory. Replace the xxx with the name of the library as listed by the LIBRARY_NAME variable.

Library project: CPPFLAGS

xxx_CPPFLAGS are additional flags that will be passed to the compiler preprocessor when compiling Objective-C and C files to generate the xxx library. Adding flags here does not override the default CPPFLAGS, see CPPFLAGS, they are in addition to CPPFLAGS. These flags are specific to the xxx library, see ADDITIONAL_CPPFLAGS, to see how to specify global preprocessor flags. Replace the xxx with the name of the listed as listed by the LIBRARY_NAME variable.

Library project: OBJCFLAGS

xxx_OBJCFLAGS are additional flags that will be passed to the compiler when compiling Objective-C files to generate the xxx library. Adding flags here does not override the default OBJCFLAGS, see OBJCFLAGS, they are in addition to OBJCFLAGS. These flags are specific to the xxx library, see ADDITIONAL_OBJCFLAGS, to see how to specify global compiler flags. Replace the xxx with the name of the library as listed by the LIBRARY_NAME variable.

Library project: CFLAGS

xxx_CFLAGS are additional flags that will be passed to the compiler when compiling C files to generate the xxx library. Adding flags here does not override the default CFLAGS, see CFLAGS, they are in addition to CFLAGS. These flags are specific to the xxx library, see ADDITIONAL_CFLAGS, to see how to specify global compiler flags. Replace the xxx with the name of the library as listed by the LIBRARY_NAME variable.

Library project: LDFLAGS

xxx_LDFLAGS are additional flags that will be passed to the linker when it creates the xxx library. Adding flags here does not override the default LDFLAGS, see LDFLAGS, they are in addition to LDFLAGS. These flags are specific to the xxx library, see ADDITIONAL_LDFLAGS, to see how to specify global linker flags. Replace the xxx with the name of the library as listed by the LIBRARY_NAME variable.

Library project: INCLUDE_DIRS

xxx_INCLUDE_DIRS is the list of additional directories that the compiler will search when it is looking for include files; these flags are specific to the xxx library, see ADDITIONAL_INCLUDE_DIRS, to see how to specify additional global include directories. The directories should be specified as ‘-I’ flags to the compiler. The additional include directories will be placed before the normal GNUstep and system include directories, and before any global include directories specified with ADDITIONAL_INCLUDE_DIRS, so they will always be searched first. Replace the xxx with the name of the library as listed by the LIBRARY_NAME variable.


Next: , Previous: , Up: library.make   [Contents]