Added single header file information to the README

This commit is contained in:
Patrick Servello 2019-02-09 10:28:01 -06:00
parent 647e977941
commit 3c655b70d9

View File

@ -181,6 +181,12 @@ using mmap_sink = mio::basic_mmap_sink<std::byte>;
Though generally not needed, since mio maps users requested offsets to page boundaries, you can query the underlying system's page allocation granularity by invoking `mio::page_size()`, which is located in `mio/page.hpp`. Though generally not needed, since mio maps users requested offsets to page boundaries, you can query the underlying system's page allocation granularity by invoking `mio::page_size()`, which is located in `mio/page.hpp`.
### Single Header File
Mio can be added to your project as a single header file simply by including `\single_include\mio\mio.hpp`. Single header files can be regenerated at any time by running the `amalgamate.py` script within `\third_party`.
```
python amalgamate.py -c config.json -s ../include
```
## CMake ## CMake
As a header-only library, mio has no compiled components. Nevertheless, a [CMake](https://cmake.org/overview/) build system is provided to allow easy testing, installation, and subproject composition on many platforms and operating systems. As a header-only library, mio has no compiled components. Nevertheless, a [CMake](https://cmake.org/overview/) build system is provided to allow easy testing, installation, and subproject composition on many platforms and operating systems.
@ -328,3 +334,4 @@ target_link_libraries( MyTarget PUBLIC <mio::mio | mio> )
``` ```
Note that, as a subproject, mio's tests and examples will not be built and CPack integration is deferred to the host project. Note that, as a subproject, mio's tests and examples will not be built and CPack integration is deferred to the host project.