Keeping multiple triplets when use vcpkg install

[autoantwort]

Describe the bug
We have a solution with multiple projects, some are x64 and some x86. We use a manifest file for the whole solution to specify the dependencies. The problem is, that when you build a x64 project, it removes the x86 versions of the dependencies and the other way around.

Environment

• OS: Windows
• Compiler: Visual Studio 2015

To Reproduce
Steps to reproduce the behavior:

1. Use a manifest file
2. Have a solution with x86 and x64 Projects
3. Build the solution

Expected behavior
Do not remove the installed versions of other triplets.

Additional context
Maybe the same as #12525, but we don't use cmake

[JackBoosY]

@strega-nil Can you please take a look?

[strega-nil]

@autoantwort What we recommend here is to set the installed directory based upon the thing you're building for; in your settings, you should be able to set the installed directory to, for example, vcpkg-installed_x64 for x64, and vcpkg-installed_win32 for win32, or whatever you wish.

Unfortunately, it seems like we don't actually have that option in the vcpkg properties pane; I will open an issue for that, and it should be a pretty easy fix.

[autoantwort]

in your settings

Which settings? Do you mean the *.vcxproj project files?

Unfortunately, it seems like we don't actually have that option in the vcpkg properties pane; I will open an issue for that, and it should be a pretty easy fix.

vcpkg/scripts/buildsystems/msbuild/vcpkg-general.xml

Line 58 in 5eea585

<StringProperty Name="VcpkgCurrentInstalledDir" DisplayName="Package install directory" Category="General" Subtype="folder" Visible="false"

Probably you only have to remove Visible="false"

But imho this is not a very user friendly and intuitive solution. It would be more user friendly if you don't remove installed packages from other triplets. Then vcpkg just works out of the box.

[autoantwort]

When I change VcpkgCurrentInstalledDir, nothing changed. If I change VcpkgInstalledDir, vcpkg initially does not work anymore, because you have to create the installed dirs yourself (copy existing installed dir and rename it).
Finally it worked with:

  <PropertyGroup Label="Vcpkg">
    <VcpkgInstalledDir>$(VcpkgRoot)$(VcpkgPlatformTarget)_installed\</VcpkgInstalledDir>
  </PropertyGroup>

I used a property sheet, because I don't want to change that manuelly in over hundred projects ...

[autoantwort]

Btw, if I change VcpkgCurrentInstalledDir and VcpkgInstalledDir, vcpkg only returns 1 and does nothing.

[strega-nil]

@autoantwort unfortunately, this isn't really a thing we can do? There's too much cross-talk, especially with #15424, to really support having two different triplets installed.

[autoantwort]

Ok. My naive assumption was that you can simply ignore packages from other triplets in the implementation, but it seems to be more complicated.

[JackBoosY]

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.

[autoantwort]

BTW this is now fixed in the latest master

[russelltg]

This would be great to have--using --x-install-root is a workaround but it's not ideal.