Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/lefticus/parser_test
https://github.com/lefticus/parser_test
Last synced: 2 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/lefticus/parser_test
- Owner: lefticus
- License: unlicense
- Created: 2020-05-29T23:56:12.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2020-06-01T02:29:43.000Z (over 4 years ago)
- Last Synced: 2024-11-05T16:56:28.576Z (about 2 months ago)
- Language: CMake
- Size: 32.2 KB
- Stars: 4
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# parser_test
[](https://codecov.io/gh/lefticus/parser_test)
[](https://travis-ci.org/lefticus/parser_test)
[](https://ci.appveyor.com/project/lefticus/parser-test/branch/master)
## Build Instructions
### Make a build directory
$ mkdir build && cd build
### Configure your build
To configure the project and write makefiles, you could use `cmake` with a
bunch of command line options. The easier option is to run cmake interactively,
with the Cmake Curses Dialog Command Line tool:
$ ccmake ..
Once `ccmake` has finished setting up, press 'c' to configure the project,
press 'g' to generate, and 'q' to quit.
### Build
Once you have selected all the options you would like to use, you can build the
project:
$ cmake --build . # build all targets
### Build using an alternate compiler
Conan and CMake use the environment variables CC and CXX to decide which
compiler to use. If you don't set these variables yourself, the system
default compiler will be used.
Be aware that CMake will detect which compiler was used to build each of the
Conan targets.
If you build all of your Conan targets with one compiler, and then build your
CMake targets with a different compiler, the project may fail to build.
To build using clang, you can use these commands:
$ CC=clang CXX=clang++ ccmake ..
$ CC=clang CXX=clang++ cmake --build .
## Troubleshooting
### Update Conan
Many problems that users have can be resolved by updating Conan, so if you are
having any trouble with this project, you should start by doing that.
To update conan:
$ pip install --user --upgrade conan
You may need to use `pip3` instead of `pip` in this command, depending on your
platform.
### Clear Conan cache
If you continue to have trouble with your Conan dependencies, you can try
clearing your Conan cache:
$ conan remove -f '*'
The next time you run `cmake` or `cmake --build`, your Conan dependencies will
be rebuilt. If you aren't using your system's default compiler, don't forget to
set the CC, CXX, CMAKE_C_COMPILER, and CMAKE_CXX_COMPILER variables, as
described in the 'Build using an alternate compiler' section above.
### Identifying misconfiguration of Conan dependencies
If you have a dependency 'A' that requires a specific version of another
dependency 'B', and your project is trying to use the wrong version of
dependency 'B', Conan will produce warnings about this configuration error
when you run CMake. These warnings can easily get lost between a couple
hundred or thousand lines of output, depending on the size of your project.
If your project has a Conan configuration error, you can use `conan info` to
find it. `conan info` displays information about the dependency graph of your
project, with colorized output in some terminals.
$ cd build
$ conan info .
In my terminal, the first couple lines of `conan info`'s output show all of the
project's configuration warnings in a bright yellow font.
For example, the package `spdlog/1.5.0` depends on the package `fmt/6.1.2`.
If you were to modify the file `cmake/Conan.cmake` so that it requires an
earlier version of `fmt`, such as `fmt/6.0.0`, and then run:
$ conan remove -f '*' # clear Conan cache
$ rm -rf build # clear previous CMake build
$ mkdir build && cd build
$ cmake .. # rebuild Conan dependencies
$ conan info .
...the first line of output would be a warning that `spdlog` needs a more recent
version of `fmt`.
## Testing
See [Catch2 tutorial](https://github.com/catchorg/Catch2/blob/master/docs/tutorial.md)
## Fuzz testing
See [libFuzzer Tutorial](https://github.com/google/fuzzing/blob/master/tutorial/libFuzzerTutorial.md)