116d1763d9
Instead of enabling signal handlers by default, require the user of the library to opt-in. This is done with the call to SCEnableDefaultSignalHandlers, which sets a flag to add the default signal handlers. This seems like the least invasive way to do this at this time, but it will require some re-thinking for 9.0, especially if migrate globals to engine instances, signal handling will need to be re-thought. Ticket: #6814 |
7 months ago | |
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile.am | ||
| Makefile.example.in | ||
| README.md | ||
| main.c | ||
README.md
Custom Library Example
This is an example of using the Suriata library with your own packets and threads.
Building In Tree
The Suricata build system has created a Makefile that should allow you to build this application in-tree on most supported platforms. To build simply run:
make
Running
./custom -l . -- filename.pcap
For this example, any arguments before -- are passed directly as
Suricata command line arguments. Arguments after the first -- are
handled by this example program, and currently the only argument is a
PCAP filename to be read.
Building Out of Tree
A Makefile.example has also been generated to use as an example on how to build against the library in a standalone application.
First build and install the Suricata library including:
make install-library
make install-headers
Then run:
make -f Makefile.example
If you installed to a non-standard location, you need to ensure that
libsuricata-config is in your path, for example:
PATH=/opt/suricata/bin:$PATH make -f Makefile.example