Basic Installation ================== These are generic installation instructions. The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile' in each directory of the package. It may also create one or more `.h' files containing system-dependent definitions. Finally, it creates a shell script `config.status' that you can run in the future to recreate the current configuration, a file `config.cache' that saves the results of its tests to speed up reconfiguring, and a file `config.log' containing compiler output (useful mainly for debugging `configure'). If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail diffs or instructions to the address given in the `README' so they can be considered for the next release. If at some point `config.cache' contains results you don't want to keep, you may remove or edit it. The file `configure.in' is used to create `configure' by a program called `autoconf'. You only need `configure.in' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile this package is: 1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute `configure' itself. Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for. 2. Type `make' to compile the package. 3. Optionally, type `make check' to run any self-tests that come with the package. 4. Type `make install' to install the programs and any data files and documentation. 5. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution. Compilers and Options ===================== Some systems require unusual options for compilation or linking that the `configure' script does not know about. You can give `configure' initial values for variables by setting them in the environment. Using a Bourne-compatible shell, you can do that on the command line like this: CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure Or on systems that have the `env' program, you can do it like this: env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure Compiling For Multiple Architectures ==================================== You can compile the package for more than one kind of computer at the same time, by placing the object files for each architecture in their own directory. To do this, you must use a version of `make' that supports the `VPATH' variable, such as GNU `make'. `cd' to the directory where you want the object files and executables to go and run the `configure' script. `configure' automatically checks for the source code in the directory that `configure' is in and in `..'. If you have to use a `make' that does not supports the `VPATH' variable, you have to compile the package for one architecture at a time in the source code directory. After you have installed the package for one architecture, use `make distclean' before reconfiguring for another architecture. Installation Names ================== By default, `make install' will install the package's files in `/usr/local/bin', `/usr/local/man', etc. You can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. You can specify separate installation prefixes for architecture-specific files and architecture-independent files. If you give `configure' the option `--exec-prefix=PATH', the package will use PATH as the prefix for installing programs and libraries. Documentation and other data files will still use the regular prefix. In addition, if you use an unusual directory layout you can give options like `--bindir=PATH' to specify different values for particular kinds of files. Run `configure --help' for a list of the directories you can set and what kinds of files go in them. If the package supports it, you can cause programs to be installed with an extra prefix or suffix on their names by giving `configure' the option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. Optional Features ================= Some packages pay attention to `--enable-FEATURE' options to `configure', where FEATURE indicates an optional part of the package. They may also pay attention to `--with-PACKAGE' options, where PACKAGE is something like `gnu-as' or `x' (for the X Window System). The `README' should mention any `--enable-' and `--with-' options that the package recognizes. For packages that use the X Window System, `configure' can usually find the X include and library files automatically, but if it doesn't, you can use the `configure' options `--x-includes=DIR' and `--x-libraries=DIR' to specify their locations. Specifying the System Type ========================== There may be some features `configure' can not figure out automatically, but needs to determine by the type of host the package will run on. Usually `configure' can figure that out, but if it prints a message saying it can not guess the host type, give it the `--host=TYPE' option. TYPE can either be a short name for the system type, such as `sun4', or a canonical name with three fields: CPU-COMPANY-SYSTEM See the file `config.sub' for the possible values of each field. If `config.sub' isn't included in this package, then this package doesn't need to know the host type. If you are building compiler tools for cross-compiling, you can also use the `--target=TYPE' option to select the type of system they will produce code for and the `--build=TYPE' option to select the type of system on which you are compiling the package. Sharing Defaults ================ If you want to set default values for `configure' scripts to share, you can create a site shell script called `config.site' that gives default values for variables like `CC', `cache_file', and `prefix'. `configure' looks for `PREFIX/share/config.site' if it exists, then `PREFIX/etc/config.site' if it exists. Or, you can set the `CONFIG_SITE' environment variable to the location of the site script. A warning: not all `configure' scripts look for a site script. Operation Controls ================== `configure' recognizes the following options to control how it operates. `--cache-file=FILE' Use and save the results of the tests in FILE instead of `./config.cache'. Set FILE to `/dev/null' to disable caching, for debugging `configure'. `--help' Print a summary of the options to `configure', and exit. `--quiet' `--silent' `-q' Do not print messages saying which checks are being made. To suppress all normal output, redirect it to `/dev/null' (any error messages will still be shown). `--srcdir=DIR' Look for the package's source code in directory DIR. Usually `configure' can determine that directory automatically. `--version' Print the version of Autoconf used to generate the `configure' script, and exit. `configure' also accepts some other, not widely useful, options. -gnome/commit/korean?id=11e70de42b8aee0bc920aff808cc8244740a1ac8'>Fix build with fmake.jkim2015-07-251-2/+2 * Update to 20141022 snapshot.jkim2015-07-233-27/+37 * Remove the unused license file since r332811.jkim2015-07-231-96/+0 * MASTER_SITES cleanup.mat2015-05-144-8/+4 * Update to 4.3.7.jkim2015-04-261-4/+4 * Major update to libpinyin, fcitx and their add ons:delphij2015-03-315-10/+20 * - Install the fonts to a better place.jkim2015-03-232-5/+8 * Fix pkg-message to display the correct directory.jkim2015-03-231-1/+1 * Update PORTREVISION to catch up with the master port change.jkim2015-03-231-1/+1 * Make fonts repecting XDGbapt2015-03-2216-124/+67 * Update KDE SC to 4.14.3alonso2015-03-122-2/+4 * - Update to 4.3.6.jkim2015-02-211-4/+4 * korean/baekmukfonts-ttfs: correct LICENSE (BSD => MIT)marino2015-02-061-1/+2 * cleanup plistbapt2014-12-216-7/+0 * Update to 4.3.5.jkim2014-12-191-4/+4 * Split devel/gettext in devel/gettext-runtime and devel/gettext-tools. Thetijl2014-11-301-1/+1 * Update to 4.3.4.jkim2014-11-271-4/+4 * Does not work anymorebapt2014-11-197-143/+0 * Cleanup plistantoine2014-11-1221-243/+11 * - Remove a few remaining $Id$ from pkg-plistsak2014-11-071-1/+0 * Update to 4.3.3.jkim2014-11-011-4/+4 * Remove @dirrm and @dirrmtry entries from the Qt ports.rakuco2014-10-241-2/+0 * - Convert ports from korean/, shells/, x11/, x11-clocks/, x11-fm/,mva2014-10-202-4/+2 * KDE/FreeBSD team presents KDE SC 4.14.2 and KDE Workspace 4.11.13!makc2014-10-193-16/+33 * Update to 4.3.2.jkim2014-10-172-5/+4 * - Set CPPFLAGS and LIBS in a number of ports so configure can find libintl.htijl2014-09-251-2/+4 * devel/glib12 x11-toolkits/gtk12:tijl2014-09-131-1/+1 * - Fix a bug which prevented a bind(2) call from working.hrs2014-09-111-1/+0 * Update the default version of GCC in the Ports Collection from GCC 4.7.4gerald2014-09-113-2/+3 * textproc/scim:tijl2014-08-311-1/+1 * Remove ports related to Adobe Reader.hrs2014-08-303-14/+0 * - Fix missing library problems when the linker enforces explicit linkingtijl2014-08-261-4/+3 * More unzip removalantoine2014-08-181-1/+0 * Upgrade OpenEXR and ilmbase to 2.2.0.mandree2014-08-161-0/+1 * Merge 4 unzip slave ports into archivers/unzip as non-default optionsmarino2014-08-154-63/+0 * Repair instances, almost all courtesy of bf ;-), of spacesadamw2014-07-301-1/+1 * Rename korean/ patch-xy patches to reflect the files they modify.adamw2014-07-292-0/+0 * Remove expired ports:rene2014-07-2510-2294/+0 * Do not try to remove directories not createdbapt2014-07-221-2/+0 * Stagify.vanilla2014-07-142-11/+1 * Remove indefinite articles and trailing periods from COMMENT, plus minorolgeni2014-07-062-2/+2 * Remove NOPORTDOCS and NOPORTEXAMPLES from unstaged ports. Stage a couple whileadamw2014-07-054-48/+35 * - Stagifyamdmi32014-07-041-5/+3 * - Switch to USES=libtoolamdmi32014-07-041-2/+2 * - Switch to USES=libtool, drop .la filesamdmi32014-07-042-5/+3 * - Switch to USES=libtoolamdmi32014-07-041-1/+2 * - Switch to USES=libtool, drop .la filesamdmi32014-07-042-3/+3 * Convert GMAKE to MAKE_CMDbapt2014-06-251-2/+2 * Update to 4.2.5.jkim2014-06-241-4/+4 * Deprecate ports failing to build with new utmpxantoine2014-06-241-0/+3 * Support LIBS like LDFLAGS.tijl2014-06-112-12/+1 * Update to libreoffice 4.2.4bapt2014-06-111-4/+4 * Add staging supportpawel2014-05-302-10/+11 * Add staging supportpawel2014-05-301-5/+4 * - Add staging supportpawel2014-05-302-8/+3 * Add staging supportpawel2014-05-301-8/+6 * Port is stage safepawel2014-05-301-1/+0 * Add staging supportpawel2014-05-301-12/+5 * Add staging supportpawel2014-05-301-4/+2 * - Add staging supportpawel2014-05-301-23/+10 * - Convert gmake to USESmiwi2014-05-264-7/+4 * STAGEDIR support.hrs2014-05-252-16/+7 * KDE/FreeBSD team presents KDE SC 4.12.5 and KDE Workspace 4.11.9!makc2014-05-111-2/+2 * - Don't remove mtree directoriesamdmi32014-05-101-1/+0 * Support stagebapt2014-05-091-1/+0 * Re-add accidentally removed PLIST_DIRS and PLIST_FILES in r339059.jkim2014-05-072-1/+5 * Update to 4.1.6.jkim2014-05-071-4/+4 * Convert all :U to :tu and :L to :tlbapt2014-05-052-5/+5 * Remove the last @comment $FreeBSD$ from plists.mat2014-04-252-2/+0 * KDE/FreeBSD team presents KDE SC 4.12.4 and KDE Workspace 4.11.8!makc2014-04-032-2/+57 * Use USES=tar:bzip2.jkim2014-03-151-2/+1 * Simplify MASTER_SITES and use USES=tar:xz.jkim2014-03-151-3/+2 * - STAGEDIR supporthrs2014-03-114-13/+8 * Convert k* to USES=zipbapt2014-03-102-2/+2 * KDE/FreeBSD team presents KDE SC 4.12.3 and KDE Workspace 4.11.7!makc2014-03-051-2/+2 * Support stagingehaupt2014-02-271-6/+4 * Update to 4.1.5. It is partially based on the following PR.jkim2014-02-261-4/+4 * Remove trailing whitespaces from category koreanehaupt2014-02-211-1/+1 * Support stagingehaupt2014-02-201-9/+4 * Support stagingehaupt2014-02-201-4/+3 * Support stagingehaupt2014-02-201-8/+3 * Support stagingehaupt2014-02-201-2/+1 * Support stagingehaupt2014-02-201-2/+1 * Support stagingehaupt2014-02-201-5/+4 * KDE/FreeBSD team presents KDE SC 4.12.2 and KDE Workspace 4.11.6!makc2014-02-184-19/+46 * According to the Porter's Handbook (5.12.2.3.) default options must be added toehaupt2014-02-101-0/+3 * - Update gimp-help ports to 2.8.1. Polish translation has been removed, newmakc2014-02-011-3/+3 * Fix properties on pkg-plistbapt2014-01-224-4/+0 * Simplify and support staging.jkim2014-01-086-60/+19 * Stagefy, convert to USES=gmake, and convert LIB_DEPENDS to new format.jkim2014-01-071-13/+5 * - Stagefy, convert to USES=gmake, convert LIB_DEPENDS to new format.jkim2014-01-071-9/+14 * Stagefy, convert to USES=gmake, and convert LIB_DEPENDS to new format.jkim2014-01-072-11/+7 * In preparation for Qt 5 ports:makc2014-01-072-17/+2 * With gtk 2.4.22, immodule cache has moved from gtk.immodules toantoine2014-01-052-13/+5 * - Add a patch from upstram.jkim2013-12-252-2/+17 * - Quiesce portlintehaupt2013-11-291-1/+0 * - Replace QT_.*_REL with QT_.* in PLIST_SUB.avilla2013-11-171-4/+4 * - Update LICENSE accordingly, now that OFL10 and OFL11 are definedtabthorpe2013-11-052-8/+2 * Support stage, use bsdtar to extractbapt2013-11-041-5/+4 * - Update to 4.0.6.jkim2013-10-262-5/+4 * - Remove manual creation and removal of share/applications, as it's now in th...amdmi32013-10-221-1/+0 * Support for this language has ceased within the PHP documentation.edwin2013-10-212-11/+0 * Update Qt to 4.8.5 and Qt Creator to 2.8.0.rakuco2013-10-141-2/+1 * korean/scim-hangul: add <unistd.h> for modern compilersmarino2013-10-031-0/+10 * Remove NO_STAGE to ports natively stage ready shown by a FORCE_STAGE exp-runbapt2013-09-241-1/+0 * Add NO_STAGE all over the place in preparation for the staging support (cat: ...bapt2013-09-2143-56/+56 * Add explicit dependency on pkgconf (20 ports)marino2013-09-121-1/+1 * Use MAKE_ARGS to simplify patches.jkim2013-09-042-11/+1 * Add an explicit dependency on pkgconfbapt2013-09-031-1/+1 * Do not extract object files from the release tarball to simplify build.jkim2013-08-311-1/+1 * Fix build with Glib20 2.36.jkim2013-08-311-3/+4 * Fix build with Clang. Remove defunct master site.jkim2013-08-316-34/+337 * Update to 4.0.5.jkim2013-08-23