Use relative header paths instead of absolute paths #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Use relative paths when including internal header files.
As an added bonus I changed some test literals to clean up warnings when building the tests.
Why?
By using relative paths the library will work anywhere it might be copied to, without the need for extra build configurations.
I ran into a problem when importing this library in my benchmark project because the dependency manager tool I'm using moves the include files to a subfolder inside a fixed include directory (the subfolder is there to avoid name collisions).