1

recently I started to use WSL & vcpkg, but it has some problems when mixing windows + linux development. It seems like that installing Linux packages or Windows packages with vcpkg, mutually damage the vcpkg configuration and then vcpkg roughly says: "the package you want to install doesn't exist". (I know for sure that it exist)

If it matters, the project is located in the windows "world" so the WSL directing to it with /mnt/c/Users//workspace/proj1 but it really doesn't matter.

Does Anyone already encountered this problem?

Am I doing something wrong?

Is there a better way to develop a cross-platform project?

Thanks

guy
  • 177
  • 2
  • 14

1 Answers1

1

So I post it to help anyone who have doubts about it: Don't mix WSL project with windows project because it will force you to work on the windows filesystem from WSL. (WSL can work on the windows filesystem with /mnt/)

anyway, It will both corrupt the vcpkg and the overall compile times will be horribly slow from linux filesystem (usually ext4) to the windows filesystem (NTFS).

this is my original post in the Github: https://github.com/microsoft/vcpkg/issues/13948#issuecomment-706625438

guy
  • 177
  • 2
  • 14
  • It will only corrupt the vcpkg installed ports database if you run it in parallel from windows and linux which is the same issue as running it from windows in parallel from two command lines. Basically vcpkg stores a database of all installed ports in a file in the installed/vcpkg dir and this file does not have any sort of locking mechanism. WSL2 /mnt performance is bad so you don't want to run it from the same dir there but for WSL1 there is no such issue – Alexander Neumann Oct 15 '20 at 10:07