You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your work! I would use libhttpserver in my ARM-uClibc-Linux embedded system.
I haven't used the library yet but I have compiled it.
And have some suggestions and notes.
1. Your last released Git tag is v0.7.1 (on 21 Mar 2014). Release new tags, please because of 0.8.0 version is pointed in docs.
2. Suggestion: to introduce --disable-doc flag as a shortcut for --disable-doxygen-doc --disable-doxygen-dot --disable-doxygen-man --disable-doxygen-html flags collection.
3. Suggestion: to introduce --disable-examples flag to disable examples compilation.
4. Suggestion: to introduce --disable-tests (and --disable-unit-tests, --disable-integ-tests?) flag to disable tests compilation.
5. You use PKG_CHECK_MODULESautoconf's macros and -lmicrohttpd linker's flag for libmicrohttpd using. But what if I want to use a static version of libmicrohttpd library or its source code instead?
6. libmicrohttpd library can be compiled without some features. dauth and bauth is just examples. But your library references to these functions in code. I think we should use conditional compilation (and configuration flag) instead. There are some lines of code for dauth and bauth only.
7. ./configure checks C++11 but it seems that USE_CPP_11 flag isn't used.
I would appreciate an answer for each of them.
Thanks very much.
Definitely right - I am working on a refactor of some of the api. A new tag will come out pretty soon then.
2),3),4) Good Ideas. I like in general the approach to allow people to disable features from compilation that they are not interested into.
The current version comes from my habit of dynamic link everything I build - get the point that it might be useful to be able to compile the lib against static libmicrohttpd versions or source code.
As per the compilation options, I believe that people should not pay for features they do not want to use - so I think this is a good idea.
This said, my current priority for the library (and what I am spending my time on) is to improve the readability of the code, eliminating some over-complicated code and simplifying logical branches and secondary to improve the test coverage.
All you suggested seems really useful though - would you be happy to implement it?
The problem is not to pay for features. The problem is: I have undefined reference errors and can't compilelibhttpserver at all if libmicrohttpd has been compiled using --disable-bauth or --disable-dauth. Note: I has been switched to static linking of libmicrohttpd in makefile manually.
@etr , thanks for the replies! Some things are 'really useful' but needless for my project (well I really can write four flags instead of one 😄 ). Sure I would be happy to implement this (and other) but if you will discuss and merge.
The problem is not to pay for features. The problem is: I have undefined reference errors and can't compilelibhttpserver at all if libmicrohttpd has been compiled using --disable-bauth or --disable-dauth. Note: I has been switched to static linking of libmicrohttpd in makefile manually.
Looks like I rediscovered that problem years later and reported it with #232? 😄
Activity
etr commentedon Feb 1, 2015
2),3),4) Good Ideas. I like in general the approach to allow people to disable features from compilation that they are not interested into.
This said, my current priority for the library (and what I am spending my time on) is to improve the readability of the code, eliminating some over-complicated code and simplifying logical branches and secondary to improve the test coverage.
All you suggested seems really useful though - would you be happy to implement it?
kuraga commentedon Feb 2, 2015
undefined referenceerrors and can't compilelibhttpserverat all iflibmicrohttpdhas been compiled using--disable-bauthor--disable-dauth. Note: I has been switched to static linking oflibmicrohttpdin makefile manually.kuraga commentedon Feb 2, 2015
@etr , thanks for the replies! Some things are 'really useful' but needless for my project (well I really can write four flags instead of one 😄 ). Sure I would be happy to implement this (and other) but if you will discuss and merge.
etr commentedon Feb 3, 2015
I will be more than happy to discuss and merge :)
LeSpocky commentedon Jan 19, 2022
Looks like I rediscovered that problem years later and reported it with #232? 😄
etr commentedon Feb 19, 2026
Last few issues addressed in: #367
TASK-051 Tier 3: address 2nd-pass review findings (fix/task-051-2nd-r…
review backlog: Pass 1 — disposition all unworked items in 22 review …
review backlog: Pass 2A — examples security fixes + REGRESSION.md drift