LIBRARY_NAMEshould 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 theLIBRARY_NAMEvariable because the Makefile Package will not automatically prefix it.
xxx_C_FILESis 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 theLIBRARY_NAMEvariable.
xxx_OBJC_FILESis 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 theLIBRARY_NAMEvariable.
xxx_CC_FILESis the list of C++ files, with a .cpp or .cc extension, that are to be compiled to generate the xxx library. Replace the xxx with the name of the library as listed by theLIBRARY_NAMEvariable.
xxx_OBJCC_FILESis the list of Objective-C++ files, with a .mm extension, that are to be compiled to generate the xxx library. Replace the xxx with the name of the library as listed by theLIBRARY_NAMEvariable.
xxx_PSWRAP_FILESis 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 theLIBRARY_NAMEvariable.
xxx_HEADER_FILESis 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 theLIBRARY_NAMEvariable.
xxx_HEADER_FILES_DIRis the relative path from the current directory, where the makefile is located, to where the header files specified byxxx_HEADER_FILESare located. If a filename specified inxxx_HEADER_FILEShas 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 withxxx_HEADER_FILES_DIRthat is already prefixed to the header filenames, see xxx_HEADER_FILES_INSTALL_DIR.xxx_HEADER_FILES_DIRis 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 theLIBRARY_NAMEvariable.
xxx_HEADER_FILES_INSTALL_DIRspecifies the relative subdirectory path belowGNUSTEP_HEADERSwhere 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 prefixesxxx_HEADER_FILES_INSTALL_DIRto each of the filenames inxxx_HEADER_FILESwhen they are installed, so if the filenames inxxx_HEADER_FILESalready have a directory path prefixed then the user is responsible for creating that directory, the Makefile Package will not create.xxx_HEADER_FILES_INSTALL_DIRis optional; leaving it blank or undefined, and the Makefile Package assumes that the installation directory is justGNUSTEP_HEADERSwith no subdirectory. Replace the xxx with the name of the library as listed by theLIBRARY_NAMEvariable.
xxx_CPPFLAGSare 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 defaultCPPFLAGS, see CPPFLAGS, they are in addition toCPPFLAGS. 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 theLIBRARY_NAMEvariable.
xxx_OBJCFLAGSare 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 defaultOBJCFLAGS, see OBJCFLAGS, they are in addition toOBJCFLAGS. 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 theLIBRARY_NAMEvariable.
xxx_CFLAGSare 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 defaultCFLAGS, see CFLAGS, they are in addition toCFLAGS. 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 theLIBRARY_NAMEvariable.
xxx_LDFLAGSare additional flags that will be passed to the linker when it creates the xxx library. Adding flags here does not override the defaultLDFLAGS, see LDFLAGS, they are in addition toLDFLAGS. 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 theLIBRARY_NAMEvariable.
xxx_INCLUDE_DIRSis 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 withADDITIONAL_INCLUDE_DIRS, so they will always be searched first. Replace the xxx with the name of the library as listed by theLIBRARY_NAMEvariable.