diff options
| author | Bo Rydberg <2945606+bolry@users.noreply.github.com> | 2019-03-11 04:31:02 +0100 |
|---|---|---|
| committer | Victor Romero <romerosanchezv@gmail.com> | 2019-03-10 20:31:02 -0700 |
| commit | c247a7d21f5835d43b6eaa5507e1b34b6803c54c (patch) | |
| tree | dcc6316f253f37db49e12e8d2ff17d60ef072ae4 /docs/specifications/export-command.md | |
| parent | eafe9ebcdf191ad0fff98c0f060000edb208318d (diff) | |
| download | vcpkg-c247a7d21f5835d43b6eaa5507e1b34b6803c54c.tar.gz vcpkg-c247a7d21f5835d43b6eaa5507e1b34b6803c54c.zip | |
Fix minor spelling mistakes in documentation (#5620)
Diffstat (limited to 'docs/specifications/export-command.md')
| -rw-r--r-- | docs/specifications/export-command.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/specifications/export-command.md b/docs/specifications/export-command.md index aaa95cb1c..4111bfed4 100644 --- a/docs/specifications/export-command.md +++ b/docs/specifications/export-command.md @@ -5,7 +5,7 @@ ### A. Build once and share Customers want to be able to build their set of required libraries once, and then distribute the resulting binaries to all members of the "group". This has been brought up in -- Enterprise environments, in which there are dedicated teams to acquire libraries and then share them with other team to consume them +- Enterprise environments, in which there are dedicated teams to acquire libraries and then share them with other teams to consume them - Academic environments, in which the professor/teacher wants to build the required libraries and then provide them to all the students - CI Systems, in which developers want to quickly distribute their exact set of dependencies to a cloud-based farm of build machines @@ -167,6 +167,6 @@ Alice gives to Bob: a) The links to her project and b) The zip file "vcpkg-expor ## 5. Technical model - Each exported library, must be accompanied with all of its dependencies, even if they are not explicitly specified in the `vcpkg export` command. -- When exporting a library, a dependency graph will be built, similarly to install, to figure out which packages needs to be exported. +- When exporting a library, a dependency graph will be built, similarly to install, to figure out which packages need to be exported. - It is allowed to have packages from different triplets, so users can include 32/64-bit and dynamic/static binaries in the same export. - The exported archives also include the files needed to integrate with MSBuild and/or CMake.
\ No newline at end of file |