While fixing the documentation, it was noticed that the hsbench
output was still referring to the project as Hyperscan.
Lets correct it.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
Correct the description in the pkgconfig file, but
leave the name alone as we want to remain compatible
with projects utilizing hyperscan.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
The generated documentation continues to refer to Hyperscan
despite the project now being VectorScan. Lets replace many
of the Hyperscan references with Vectorscan.
At the same time, lets resync the documentation here with the
vectorscan readme. This updates the supported platforms/compilers
and build options.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
The project name in the documentation should probably
be updated to reflect that this is vectorscan. Update
the copyright too.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
Man pages tend to be preferred in some circles, lets add an
option to build the vectorscan documentation that way.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
This adds three new CMake options, all defaulting to true, making it
possible to opt-out of building parts of Vectorscan that are not
essential for deployment of the matching runtime.
These new options:
- `BUILD_UNIT`: control whether the `unit` directory is included
- `BUILD_DOC`: control whether the `doc` directory is included
- `BUILD_TOOLS`: control whether the `tools` directory is included
According to https://buildbot-ci.vectorcamp.gr/#/changes/93
most builds succceded and with no compiler warnings. The build failures were only on x86 and Arm for SIMDe builds: x86 because of a bug in SIMDe emulation of own x86 intrinsics in non-native mode and Arm due to clang, unsure if this is actually a bug in SIMDe or clang itself. All the remaining compiler warnings that were suppressed was because they were not possible to fix for the scope of this project.
This PR will close#170, code quality improvements however will continue with the integration of #222 or similar static code analyzer to CI and continuous refactoring.
