diff options
author | Christian Grothoff <christian@grothoff.org> | 2007-09-09 21:32:12 +0000 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2007-09-09 21:32:12 +0000 |
commit | fb36fb2009a35e48be28df422af5a4b42d099cda (patch) | |
tree | 103c9372286a794293b36bcc0e18e091bde49f3d /README | |
parent | 8ce09efc5e3c19d413727e8b80c5f2eff9406b38 (diff) | |
download | libmicrohttpd-fb36fb2009a35e48be28df422af5a4b42d099cda.tar.gz libmicrohttpd-fb36fb2009a35e48be28df422af5a4b42d099cda.zip |
release
Diffstat (limited to 'README')
-rw-r--r-- | README | 34 |
1 files changed, 32 insertions, 2 deletions
@@ -1,6 +1,36 @@ | |||
1 | Run "autoreconf -fi" to create configure. | 1 | About |
2 | ===== | ||
2 | 3 | ||
3 | This is still alpha software. Below we list things that should be | 4 | libmicrohttpd is a library written in C that provides a compact |
5 | API and implementation of an HTTP 1.1 web server. libmicrohttpd | ||
6 | only implements the HTTP 1.1 protocol. The main application must | ||
7 | still provide the content. | ||
8 | |||
9 | |||
10 | Installation | ||
11 | ============ | ||
12 | |||
13 | If you are using Subversion, run "autoreconf -fi" to create configure. | ||
14 | |||
15 | In order to run the testcases, you need a recent version of libcurl. | ||
16 | libcurl is not required if you just want to install the library. | ||
17 | |||
18 | |||
19 | Configure options | ||
20 | ================= | ||
21 | |||
22 | Especially for development, use "--enable-messages" to enable error | ||
23 | reporting (and use MHD_USE_DEBUG). Error reporting is not enabled by | ||
24 | default to reduce the size of the library (error messages take | ||
25 | space!). If you are concerned about space, you should set "CFLAGS" to | ||
26 | "-Os --fomit-frame-pointer" to have gcc generate tight code. The | ||
27 | resulting binary should be less than 25k (on x86). | ||
28 | |||
29 | |||
30 | Development Status | ||
31 | ================== | ||
32 | |||
33 | This is a beta release. Below we list things that should be | ||
4 | implemented (in order of importance) before we can claim to be | 34 | implemented (in order of importance) before we can claim to be |
5 | reasonably complete. #XXXX refers to the respective Mantis bug report | 35 | reasonably complete. #XXXX refers to the respective Mantis bug report |
6 | (or feature request). ARCH indicates that implementing this feature | 36 | (or feature request). ARCH indicates that implementing this feature |