[ Pobierz całość w formacie PDF ]
.Example:Specifies additional include flags for the C compiler ( directory ).These flags can also be specified via , but for historical reasonsthey have their own variable.LDFLAGS Linker Standard FlagsExample:Specifies additional standard flags for the linker command.These flagsare usually directory flags intended to help the linker find third-party libraries.LIBS Linker Library FlagsExample:Specifies additional library flags for the linker command.These flagsare usually just name flags for linking Apache with third-party li-braries.CFLAGS Additional CFLAGS for DSO BuildingSHLIBExample:Papersize: (US letter)Cropmarks: (AWL repro) 46 Chapter 3: Building ApacheSpecial flags for the C compiler that are used in addition towhen DSOs are compiled.Usually, they specify which flags are re-quired to force the generation of position-independent code (PIC).LD SHLIB Linker for DSO BuildingExample:Specifies the linker used for building DSOs.The default is platform-In most cases, you do dependent and is usually either the value of or directly .not need to specifyDSO building detailsLDFLAGS Additional LDFLAGS for DSO BuildingSHLIBmanually.ApacheExample:already knows how touse DSO on all majorSpecial flags for the DSO linker command ( ) that are used inUNIX platforms.addition to when DSOs are built.Usually, they specify whichflags are required to force the generation of shared objects instead ofstandard objects (executables).LDFLAGS SHLIB EXPORT Add.LDFLAGS for ProgramBuilding under DSOExample:Special flags for the linker command ( ) that are used in addition towhen the Apache executable is built.Usually, they specifywhich flags are required to force the export of API symbols for use byDSO-based modules.RANLIB Archive Indexing ToolExample:Used to override the command if the local platform doesn trequire it.This command is rarely needed, because Apache automati-cally knows whether it is required.DEPS Additional Makefile DependencyExample:For developers only.This command can be used to add a Make depen-dency to.TARGET Name of the Target ProgramExample:Equivalent to the option.(See this option for details.)EAPI MM Path to MM Library (mod ssl only)Example:Sets the path to the MM library source or installation tree.This libraryis used in conjunction with the Extended API (EAPI) facility.The argu-ment can be specified to indicate that APACI should searchfor the MM library in standard system locations.Papersize: (US letter)Cropmarks: (AWL repro) 3.2 Configuration Reference 47SSL BASE Path to OpenSSL Toolkit (mod ssl only)Example:Sets the path to the OpenSSL toolkit source or installation tree.Thistoolkit is used in conjunction with.The string canbe specified as the argument to indicate that APACI should search forthe OpenSSL toolkit in standard system locations.extendsAPACI; that s whyadditional configurationRSA BASE Path to RSAref Library (mod ssl only)variables are available.Example:Sets the path to the RSAref library source or installation tree.Thislibrary is used by U.S.residents (only) in conjunction with.The string can be specified as the argument to indicate thatAPACI should search for the RSAref library in standard system loca-tions.3.2.2 General OptionsThe following general options are available on the APACI command line:--quiet Quiet ConfigurationExample:Forces APACI to suppress the display of all output while configuringthe source tree.This option can be useful for running APACI in batchmode for instance, from a vendor packaging facility like RPM.--verbose Verbose ConfigurationExample:Forces APACI to display additional output while configuring the Apa-che source tree.This option can be useful for testing the results of var-ious configuration options.Use forbuilding Apache onmultiple architectures--shadow[=Dir] Create a Shadow Source Treein parallel.Example:Creates a shadow tree of the Apache source tree under the specifieddirectory Dir before configuration.A shadow tree consists of all direc-tories of the original tree, with all files inside those directories beingreplaced by symbolic links to the original files.This option is usefulwhen the original Apache source tree stays on a read-only medium(typically, a CD-ROM) or when one compiles Apache in parallel formultiple platforms.Details about this facility are found in section 3.3.1.Papersize: (US letter)Cropmarks: (AWL repro) 48 Chapter 3: Building Apache3.2.3 Stand-alone OptionsThe following options stand alone.That is, they stop the configuration pro-cess and instead perform a special action only.--help Display Usage SummaryExample:Displays a short usage summary page listing all APACI command-lineoptions.Use this option when you have forgotten an option and wantto identify it.--show-layout Display Installation Path LayoutExample:Displays the resulting installation path layout.By default, this optiondisplays the Apache layout from the file.It is alsouseful in combination with the option and the otherinstallation layout options (see section 3.2.4) for easily checking the re-sults of those options without having to configure, build, and installthe package.3.2
[ Pobierz całość w formacie PDF ]