diff options
| author | Robert Schumacher <roschuma@microsoft.com> | 2017-08-30 21:00:59 -0700 |
|---|---|---|
| committer | Robert Schumacher <roschuma@microsoft.com> | 2017-08-30 21:00:59 -0700 |
| commit | b966cdce678461e5497b01a25664ace0e76b51bf (patch) | |
| tree | d3dfbf488e3acad7207d5a9f0d28a0bc31c7bee9 /docs | |
| parent | 23649f58ec58196ff6e7f0b25f2d13f4b0c27cc9 (diff) | |
| download | vcpkg-b966cdce678461e5497b01a25664ace0e76b51bf.tar.gz vcpkg-b966cdce678461e5497b01a25664ace0e76b51bf.zip | |
[vcpkg-docs] Add integrate project to faq section
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/about/faq.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/about/faq.md b/docs/about/faq.md index 43039258f..8234216e0 100644 --- a/docs/about/faq.md +++ b/docs/about/faq.md @@ -62,7 +62,9 @@ Of course, this will only produce viable binaries if your custom configuration i ## I can't use user-wide integration. Can I use a per-project integration? -Yes. The Visual Studio integration is actually enabled by the `<vcpkg_root>\scripts\buildsystems\msbuild\vcpkg.targets` file. So all you need is to import it in your .vcxproj file, replacing `<vcpkg_root>` with the path where you installed vcpkg: +Yes. A NuGet package suitable for per-project use can be generated via either the `vcpkg integrate project` command (lightweight linking) or the `vcpkg export --nuget` command (shrinkwrapped). + +A lower level mechanism to achieve the same as the `vcpkg integrate project` NuGet package is via the `<vcpkg_root>\scripts\buildsystems\msbuild\vcpkg.targets` file. All you need is to import it in your .vcxproj file, replacing `<vcpkg_root>` with the path where you installed vcpkg: ``` <Import Project="<vcpkg_root>\scripts\buildsystems\msbuild\vcpkg.targets" /> |