tqcq/CPM.cmake
0
0
Fork 0
mirror of https://github.com/cpm-cmake/CPM.cmake.git synced 2025-11-23 04:37:43 -05:00
Code Issues Packages Projects Releases Wiki Activity

fix,doc: spelling errors (#551)

Browse Source
This commit is contained in:
Simon Gene Gottlieb
2024-04-07 23:36:07 +02:00
committed by GitHub
parent a8144f511d
commit 0e450ef450
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
CONTRIBUTING.md
View File

@@ -104,7 +104,7 @@ Please try to keep your individual changes as minimal and focussed on the issue
If you discover that the scope of your contribution is growing larger than expected you might want to split the changes into multiple separate contributions to allow a more focussed discussion and review. If you discover that the scope of your contribution is growing larger than expected you might want to split the changes into multiple separate contributions to allow a more focussed discussion and review.
It is usually a great idea and often required to add tests for your changes. It is usually a great idea and often required to add tests for your changes.
This allows us to quickly validate that the changes are working as intended and also guarantees that they wont be broken by other future updates. This allows us to quickly validate that the changes are working as intended and also guarantees that they won't be broken by other future updates.
For small and targeted functional changes, e.g. supporting a new URL schema, a [unit test](#unit-tests) may be enough. For small and targeted functional changes, e.g. supporting a new URL schema, a [unit test](#unit-tests) may be enough.
For contributions that change large-scale behaviour, such as dependency caching features, an [integration test](#integration-tests) is more suited. For contributions that change large-scale behaviour, such as dependency caching features, an [integration test](#integration-tests) is more suited.
Depending on the changes, a combination of both test types may also be appropriate. Depending on the changes, a combination of both test types may also be appropriate.
@@ -174,4 +174,4 @@ cmake --build build/style --target fix-format
<!-- omit in toc --> <!-- omit in toc -->
## Attribution ## Attribution
This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)! This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)!

6
README.md
View File

@@ -409,7 +409,7 @@ CPMAddPackage(
### [Boost](https://github.com/boostorg/boost) ### [Boost](https://github.com/boostorg/boost)
Boost is a large project and will take a while to download. Using Boost is a large project and will take a while to download. Using
`CPM_SOURCE_CACHE` is strongly recomended. Cloning moves much more `CPM_SOURCE_CACHE` is strongly recommended. Cloning moves much more
data than a source archive, so this sample will use a compressed data than a source archive, so this sample will use a compressed
source archive (tar.xz) release from Boost's github page. source archive (tar.xz) release from Boost's github page.
@@ -538,7 +538,7 @@ The URL for branch `v2.x` of spdlog is:
#### Tag #### Tag
Tags are simiar, but with this format: Tags are similar, but with this format:
`https://github.com/<user>/<name>/archive/refs/tags/<tag-name>.<archive-type>` `https://github.com/<user>/<name>/archive/refs/tags/<tag-name>.<archive-type>`
@@ -561,7 +561,7 @@ Example:
### Determining the Hash ### Determining the Hash
The following snipet illustrates determining the SHA256 hash on a linux machine using `wget` and `sha256sum`: The following snippet illustrates determining the SHA256 hash on a linux machine using `wget` and `sha256sum`:
```bash ```bash
wget https://github.com/gabime/spdlog/archive/refs/tags/v1.13.0.zip -O - | sha256sum wget https://github.com/gabime/spdlog/archive/refs/tags/v1.13.0.zip -O - | sha256sum
``` ```

2
test/integration/test_simple.rb
View File

@@ -70,7 +70,7 @@ class Simple < IntegrationTest
exes = Dir[exe_dir + '/**/*'].filter { exes = Dir[exe_dir + '/**/*'].filter {
# on multi-configuration generators (like Visual Studio) the executables will be in bin/<Config> # on multi-configuration generators (like Visual Studio) the executables will be in bin/<Config>
# also filter-out other articacts like .pdb or .dsym # also filter-out other artifacts like .pdb or .dsym
!File.directory?(_1) && File.stat(_1).executable? !File.directory?(_1) && File.stat(_1).executable?
}.map { }.map {
# remove .exe extension if any (there will be one on Windows) # remove .exe extension if any (there will be one on Windows)