| … | |
… | |
| 4652 | With an intelligent-enough linker (gcc+binutils are intelligent enough |
4652 | With an intelligent-enough linker (gcc+binutils are intelligent enough |
| 4653 | when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by |
4653 | when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by |
| 4654 | your program might be left out as well - a binary starting a timer and an |
4654 | your program might be left out as well - a binary starting a timer and an |
| 4655 | I/O watcher then might come out at only 5Kb. |
4655 | I/O watcher then might come out at only 5Kb. |
| 4656 | |
4656 | |
|
|
4657 | =item EV_API_STATIC |
|
|
4658 | |
|
|
4659 | If this symbol is defined (by default it is not), then all identifiers |
|
|
4660 | will have static linkage. This means that libev will not export any |
|
|
4661 | identifiers, and you cannot link against libev anymore. This can be useful |
|
|
4662 | when you embed libev, only want to use libev functions in a single file, |
|
|
4663 | and do not want its identifiers to be visible. |
|
|
4664 | |
|
|
4665 | To use this, define C<EV_API_STATIC> and include F<ev.c> in the file that |
|
|
4666 | wants to use libev. |
|
|
4667 | |
| 4657 | =item EV_AVOID_STDIO |
4668 | =item EV_AVOID_STDIO |
| 4658 | |
4669 | |
| 4659 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
4670 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
| 4660 | functions (printf, scanf, perror etc.). This will increase the code size |
4671 | functions (printf, scanf, perror etc.). This will increase the code size |
| 4661 | somewhat, but if your program doesn't otherwise depend on stdio and your |
4672 | somewhat, but if your program doesn't otherwise depend on stdio and your |
