Windows 10 cannot detect the header file of Linux in WSL after updating 1.8.0 or 1.8.1 #8767
Answered
by
sean-mcmanus
Xiao Yongcheng (xiaoyongcheng)
asked this question in
Q&A
|
I don't know if it's a bug, but this problem occurred after the automatic update one day. It was solved by returning version 1.7.1. need I to add all the header file paths to the includepath? hope you can answer the question. thx Orz |
Answered by
sean-mcmanus
Feb 3, 2022
Replies: 1 comment 1 reply
|
We don't support accessing Linux/WSL paths from Windows...we had some legacy support, but we're not maintaining it. We intend for access to Linux/WSL files to be done via using the Remote WSL extension and running our extension from there (running in WSL). |
1 reply
Answer selected by
xiaoyongcheng
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We don't support accessing Linux/WSL paths from Windows...we had some legacy support, but we're not maintaining it. We intend for access to Linux/WSL files to be done via using the Remote WSL extension and running our extension from there (running in WSL).