Peter M. Groen / CLI11

Commit b7c031cc3e758b4ea7728c818e0edcbfe7f96c4c

Authored by Henry Fredrick Schreiner
1 parent 169e4ec6

Fix typo in conan upload info 

[skip ci]
Inline Side-by-side
Showing 2 changed files with 6 additions and 4 deletions
.github/CONTRIBUTING.md
  View file @b7c031c
... ... @@ -34,7 +34,7 @@ The steps to make a Conan.io release are:
34 34 ```bash
35 35 conan delete '*' # optional, I like to be clean
36 36  
37   -conan create . CLIUtils/stable
  37 +conan create . cliutils/stable
38 38 conan upload "*" -r cli11 --all
39 39 ```
40 40  
... ...
README.md
  View file @b7c031c
... ... @@ -87,7 +87,9 @@ There are some other possible "features" that are intentionally not supported by
87 87 To use, there are two methods:
88 88  
89 89 1. Copy `CLI11.hpp` from the [most recent release][Github Releases] into your include directory, and you are set. This is combined from the source files for every release. This includes the entire command parser library, but does not include separate utilities (like `Timer`, `AutoTimer`). The utilities are completely self contained and can be copied separately.
90   -2. Use `CLI/*.hpp` files. You could check out the repository as a submodule, for example. You can use the `CLI11::CLI11` interface target when linking from `add_subdirectory`. You can also configure and optionally install the project, and then use `find_package(CLI11 CONFIG)` to get the `CLI11::CLI11` target. You can also use [Conan.io][conan-link]. (These are just conveniences to allow you to use your favorite method of managing packages; it's just header only so including the correct path and
  90 +2. Use `CLI/*.hpp` files. You could check out the repository as a submodule, for example. You can use the `CLI11::CLI11` interface target when linking from `add_subdirectory`.
  91 + You can also configure and optionally install the project, and then use `find_package(CLI11 CONFIG)` to get the `CLI11::CLI11` target. You can also use [Conan.io][conan-link].
  92 + (These are just conveniences to allow you to use your favorite method of managing packages; it's just header only so including the correct path and
91 93 using C++11 is all you really need.)
92 94  
93 95 To build the tests, checkout the repository and use CMake:
... ... @@ -405,8 +407,8 @@ CLI11 was developed at the [University of Cincinnati] to support of the [GooFit]
405 407 [gitter-badge]: https://badges.gitter.im/CLI11gitter/Lobby.svg
406 408 [gitter]: https://gitter.im/CLI11gitter/Lobby
407 409 [license-badge]: https://img.shields.io/badge/License-BSD-blue.svg
408   -[conan-badge]: https://api.bintray.com/packages/cliutils/CLI11/CLI11/images/download.svg
409   -[conan-link]: https://bintray.com/cliutils/CLI11/CLI11/_latestVersion
  410 +[conan-badge]: https://api.bintray.com/packages/cliutils/CLI11/CLI11%3Acliutils/images/download.svg
  411 +[conan-link]: https://bintray.com/cliutils/CLI11/CLI11%3Acliutils/_latestVersion
410 412 [Github Releases]: https://github.com/CLIUtils/CLI11/releases
411 413 [Github Issues]: https://github.com/CLIUtils/CLI11/issues
412 414 [Github Pull Requests]: https://github.com/CLIUtils/CLI11/pulls
... ...