{"schema":"libjg2-1", "vpath":"/git/", "avatar":"/git/avatar/", "alang":"", "gen_ut":1752653226, "reponame":"libwebsockets", "desc":"libwebsockets lightweight C networking library", "owner": { "name": "Andy Green", "email": "andy@warmcat.com", "md5": "c50933ca2aa61e0fe2c43d46bb6b59cb" },"url":"https://libwebsockets.org/repo/libwebsockets", "f":3, "items": [ {"schema":"libjg2-1", "cid":"b849cfea49d38accf1b19443ace9d9ed", "oid":{ "oid": "68a672bb4468e98c339987404c32f39a6b86e5fb", "alias": []},"blobname": "INSTALL", "blob": "Installation Instructions\n*************************\n\nCopyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,\n2006, 2007, 2008, 2009 Free Software Foundation, Inc.\n\n Copying and distribution of this file, with or without modification,\nare permitted in any medium without royalty provided the copyright\nnotice and this notice are preserved. This file is offered as-is,\nwithout warranty of any kind.\n\nBasic Installation\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n Briefly, the shell commands `./configure; make; make install' should\nconfigure, build, and install this package. The following\nmore-detailed instructions are generic; see the `README' file for\ninstructions specific to this package. Some packages provide this\n`INSTALL' file but do not implement all of the features documented\nbelow. The lack of an optional feature in a given package is not\nnecessarily a bug. More recommendations for GNU packages can be found\nin *note Makefile Conventions: (standards)Makefile Conventions.\n\n The `configure' shell script attempts to guess correct values for\nvarious system-dependent variables used during compilation. It uses\nthose values to create a `Makefile' in each directory of the package.\nIt may also create one or more `.h' files containing system-dependent\ndefinitions. Finally, it creates a shell script `config.status' that\nyou can run in the future to recreate the current configuration, and a\nfile `config.log' containing compiler output (useful mainly for\ndebugging `configure').\n\n It can also use an optional file (typically called `config.cache'\nand enabled with `--cache-file\u003dconfig.cache' or simply `-C') that saves\nthe results of its tests to speed up reconfiguring. Caching is\ndisabled by default to prevent problems with accidental use of stale\ncache files.\n\n If you need to do unusual things to compile the package, please try\nto figure out how `configure' could check whether to do them, and mail\ndiffs or instructions to the address given in the `README' so they can\nbe considered for the next release. If you are using the cache, and at\nsome point `config.cache' contains results you don't want to keep, you\nmay remove or edit it.\n\n The file `configure.ac' (or `configure.in') is used to create\n`configure' by a program called `autoconf'. You need `configure.ac' if\nyou want to change it or regenerate `configure' using a newer version\nof `autoconf'.\n\n The simplest way to compile this package is:\n\n 1. `cd' to the directory containing the package's source code and type\n `./configure' to configure the package for your system.\n\n Running `configure' might take a while. While running, it prints\n some messages telling which features it is checking for.\n\n 2. Type `make' to compile the package.\n\n 3. Optionally, type `make check' to run any self-tests that come with\n the package, generally using the just-built uninstalled binaries.\n\n 4. Type `make install' to install the programs and any data files and\n documentation. When installing into a prefix owned by root, it is\n recommended that the package be configured and built as a regular\n user, and only the `make install' phase executed with root\n privileges.\n\n 5. Optionally, type `make installcheck' to repeat any self-tests, but\n this time using the binaries in their final installed location.\n This target does not install anything. Running this target as a\n regular user, particularly if the prior `make install' required\n root privileges, verifies that the installation completed\n correctly.\n\n 6. You can remove the program binaries and object files from the\n source code directory by typing `make clean'. To also remove the\n files that `configure' created (so you can compile the package for\n a different kind of computer), type `make distclean'. There is\n also a `make maintainer-clean' target, but that is intended mainly\n for the package's developers. If you use it, you may have to get\n all sorts of other programs in order to regenerate files that came\n with the distribution.\n\n 7. Often, you can also type `make uninstall' to remove the installed\n files again. In practice, not all packages have tested that\n uninstallation works correctly, even though it is required by the\n GNU Coding Standards.\n\n 8. Some packages, particularly those that use Automake, provide `make\n distcheck', which can by used by developers to test that all other\n targets like `make install' and `make uninstall' work correctly.\n This target is generally not run by end users.\n\nCompilers and Options\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n Some systems require unusual options for compilation or linking that\nthe `configure' script does not know about. Run `./configure --help'\nfor details on some of the pertinent environment variables.\n\n You can give `configure' initial values for configuration parameters\nby setting variables in the command line or in the environment. Here\nis an example:\n\n ./configure CC\u003dc99 CFLAGS\u003d-g LIBS\u003d-lposix\n\n *Note Defining Variables::, for more details.\n\nCompiling For Multiple Architectures\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n You can compile the package for more than one kind of computer at the\nsame time, by placing the object files for each architecture in their\nown directory. To do this, you can use GNU `make'. `cd' to the\ndirectory where you want the object files and executables to go and run\nthe `configure' script. `configure' automatically checks for the\nsource code in the directory that `configure' is in and in `..'. This\nis known as a \u0022VPATH\u0022 build.\n\n With a non-GNU `make', it is safer to compile the package for one\narchitecture at a time in the source code directory. After you have\ninstalled the package for one architecture, use `make distclean' before\nreconfiguring for another architecture.\n\n On MacOS X 10.5 and later systems, you can create libraries and\nexecutables that work on multiple system types--known as \u0022fat\u0022 or\n\u0022universal\u0022 binaries--by specifying multiple `-arch' options to the\ncompiler but only a single `-arch' option to the preprocessor. Like\nthis:\n\n ./configure CC\u003d\u0022gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64\u0022 \u005c\n CXX\u003d\u0022g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64\u0022 \u005c\n CPP\u003d\u0022gcc -E\u0022 CXXCPP\u003d\u0022g++ -E\u0022\n\n This is not guaranteed to produce working output in all cases, you\nmay have to build one architecture at a time and combine the results\nusing the `lipo' tool if you have problems.\n\nInstallation Names\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n By default, `make install' installs the package's commands under\n`/usr/local/bin', include files under `/usr/local/include', etc. You\ncan specify an installation prefix other than `/usr/local' by giving\n`configure' the option `--prefix\u003dPREFIX', where PREFIX must be an\nabsolute file name.\n\n You can specify separate installation prefixes for\narchitecture-specific files and architecture-independent files. If you\npass the option `--exec-prefix\u003dPREFIX' to `configure', the package uses\nPREFIX as the prefix for installing programs and libraries.\nDocumentation and other data files still use the regular prefix.\n\n In addition, if you use an unusual directory layout you can give\noptions like `--bindir\u003dDIR' to specify different values for particular\nkinds of files. Run `configure --help' for a list of the directories\nyou can set and what kinds of files go in them. In general, the\ndefault for these options is expressed in terms of `${prefix}', so that\nspecifying just `--prefix' will affect all of the other directory\nspecifications that were not explicitly provided.\n\n The most portable way to affect installation locations is to pass the\ncorrect locations to `configure'; however, many packages provide one or\nboth of the following shortcuts of passing variable assignments to the\n`make install' command line to change installation locations without\nhaving to reconfigure or recompile.\n\n The first method involves providing an override variable for each\naffected directory. For example, `make install\nprefix\u003d/alternate/directory' will choose an alternate location for all\ndirectory configuration variables that were expressed in terms of\n`${prefix}'. Any directories that were specified during `configure',\nbut not in terms of `${prefix}', must each be overridden at install\ntime for the entire installation to be relocated. The approach of\nmakefile variable overrides for each directory variable is required by\nthe GNU Coding Standards, and ideally causes no recompilation.\nHowever, some platforms have known limitations with the semantics of\nshared libraries that end up requiring recompilation when using this\nmethod, particularly noticeable in packages that use GNU Libtool.\n\n The second method involves providing the `DESTDIR' variable. For\nexample, `make install DESTDIR\u003d/alternate/directory' will prepend\n`/alternate/directory' before all installation names. The approach of\n`DESTDIR' overrides is not required by the GNU Coding Standards, and\ndoes not work on platforms that have drive letters. On the other hand,\nit does better at avoiding recompilation issues, and works well even\nwhen some directory options were not specified in terms of `${prefix}'\nat `configure' time.\n\nOptional Features\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n If the package supports it, you can cause programs to be installed\nwith an extra prefix or suffix on their names by giving `configure' the\noption `--program-prefix\u003dPREFIX' or `--program-suffix\u003dSUFFIX'.\n\n Some packages pay attention to `--enable-FEATURE' options to\n`configure', where FEATURE indicates an optional part of the package.\nThey may also pay attention to `--with-PACKAGE' options, where PACKAGE\nis something like `gnu-as' or `x' (for the X Window System). The\n`README' should mention any `--enable-' and `--with-' options that the\npackage recognizes.\n\n For packages that use the X Window System, `configure' can usually\nfind the X include and library files automatically, but if it doesn't,\nyou can use the `configure' options `--x-includes\u003dDIR' and\n`--x-libraries\u003dDIR' to specify their locations.\n\n Some packages offer the ability to configure how verbose the\nexecution of `make' will be. For these packages, running `./configure\n--enable-silent-rules' sets the default to minimal output, which can be\noverridden with `make V\u003d1'; while running `./configure\n--disable-silent-rules' sets the default to verbose, which can be\noverridden with `make V\u003d0'.\n\nParticular systems\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n On HP-UX, the default C compiler is not ANSI C compatible. If GNU\nCC is not installed, it is recommended to use the following options in\norder to use an ANSI C compiler:\n\n ./configure CC\u003d\u0022cc -Ae -D_XOPEN_SOURCE\u003d500\u0022\n\nand if that doesn't work, install pre-built binaries of GCC for HP-UX.\n\n On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot\nparse its `\u003cwchar.h\u003e' header file. The option `-nodtk' can be used as\na workaround. If GNU CC is not installed, it is therefore recommended\nto try\n\n ./configure CC\u003d\u0022cc\u0022\n\nand if that doesn't work, try\n\n ./configure CC\u003d\u0022cc -nodtk\u0022\n\n On Solaris, don't put `/usr/ucb' early in your `PATH'. This\ndirectory contains several dysfunctional programs; working variants of\nthese programs are available in `/usr/bin'. So, if you need `/usr/ucb'\nin your `PATH', put it _after_ `/usr/bin'.\n\n On Haiku, software installed for all users goes in `/boot/common',\nnot `/usr/local'. It is recommended to use the following options:\n\n ./configure --prefix\u003d/boot/common\n\nSpecifying the System Type\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n There may be some features `configure' cannot figure out\nautomatically, but needs to determine by the type of machine the package\nwill run on. Usually, assuming the package is built to be run on the\n_same_ architectures, `configure' can figure that out, but if it prints\na message saying it cannot guess the machine type, give it the\n`--build\u003dTYPE' option. TYPE can either be a short name for the system\ntype, such as `sun4', or a canonical name which has the form:\n\n CPU-COMPANY-SYSTEM\n\nwhere SYSTEM can have one of these forms:\n\n OS\n KERNEL-OS\n\n See the file `config.sub' for the possible values of each field. If\n`config.sub' isn't included in this package, then this package doesn't\nneed to know the machine type.\n\n If you are _building_ compiler tools for cross-compiling, you should\nuse the option `--target\u003dTYPE' to select the type of system they will\nproduce code for.\n\n If you want to _use_ a cross compiler, that generates code for a\nplatform different from the build platform, you should specify the\n\u0022host\u0022 platform (i.e., that on which the generated programs will\neventually be run) with `--host\u003dTYPE'.\n\nSharing Defaults\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n If you want to set default values for `configure' scripts to share,\nyou can create a site shell script called `config.site' that gives\ndefault values for variables like `CC', `cache_file', and `prefix'.\n`configure' looks for `PREFIX/share/config.site' if it exists, then\n`PREFIX/etc/config.site' if it exists. Or, you can set the\n`CONFIG_SITE' environment variable to the location of the site script.\nA warning: not all `configure' scripts look for a site script.\n\nDefining Variables\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n Variables not defined in a site shell script can be set in the\nenvironment passed to `configure'. However, some packages may run\nconfigure again during the build, and the customized values of these\nvariables may be lost. In order to avoid this problem, you should set\nthem in the `configure' command line, using `VAR\u003dvalue'. For example:\n\n ./configure CC\u003d/usr/local2/bin/gcc\n\ncauses the specified `gcc' to be used as the C compiler (unless it is\noverridden in the site shell script).\n\nUnfortunately, this technique does not work for `CONFIG_SHELL' due to\nan Autoconf bug. Until the bug is fixed you can use this workaround:\n\n CONFIG_SHELL\u003d/bin/bash /bin/bash ./configure CONFIG_SHELL\u003d/bin/bash\n\n`configure' Invocation\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\n `configure' recognizes the following options to control how it\noperates.\n\n`--help'\n`-h'\n Print a summary of all of the options to `configure', and exit.\n\n`--help\u003dshort'\n`--help\u003drecursive'\n Print a summary of the options unique to this package's\n `configure', and exit. The `short' variant lists options used\n only in the top level, while the `recursive' variant lists options\n also present in any nested packages.\n\n`--version'\n`-V'\n Print the version of Autoconf used to generate the `configure'\n script, and exit.\n\n`--cache-file\u003dFILE'\n Enable the cache: use and save the results of the tests in FILE,\n traditionally `config.cache'. FILE defaults to `/dev/null' to\n disable caching.\n\n`--config-cache'\n`-C'\n Alias for `--cache-file\u003dconfig.cache'.\n\n`--quiet'\n`--silent'\n`-q'\n Do not print messages saying which checks are being made. To\n suppress all normal output, redirect it to `/dev/null' (any error\n messages will still be shown).\n\n`--srcdir\u003dDIR'\n Look for the package's source code in directory DIR. Usually\n `configure' can determine that directory automatically.\n\n`--prefix\u003dDIR'\n Use DIR as the installation prefix. *note Installation Names::\n for more details, including other options available for fine-tuning\n the installation locations.\n\n`--no-create'\n`-n'\n Run the configure checks, but stop before creating any output\n files.\n\n`configure' also accepts some other, not widely useful, options. Run\n`configure --help' for more details.\n\n","s":{"c":1752571122,"u": 528}} ],"g": 2508,"chitpc": 0,"ehitpc": 0,"indexed":0 , "ab": 0, "si": 0, "db":0, "di":0, "sat":0, "lfc": "7d0a"}