New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not include #include <sys/io.h> <sys/sysinfo.h> <sys/stat.h> <unistd> etc. #127
Comments
It seems not all headers are installed by VCLinux. Copying them from your Linux system should fix your problem. See: http://stackoverflow.com/questions/43022494/linux-header-file-not-recognized-in-visual-studio-2017-linux-project/43034796#43034796 . Since there are subtle differences in which headers are present and where they are located on different Linux systems it might help the VCLinux team if you document your Linux system and the missing headers with their paths. |
Automatically copying headers and providing good IntelliSense beyond the C++/C standard libraries is something that we know that we absolutely need to improve. But it's a bit of work, we have it planned in the near future so I'm going to tag it with feature. In mean time, you can copy those headers locally and point IntelliSense to them, that should work as a temporary work around. |
Using #43 for tracking |
As an update, we implemented this feature |
@itodirel hi,how do we get this feature? how to do the update? thanks |
It's in the latest Visual Studio 2017 preview and is described in this Visual C++ blog entry . I can confirm it works as advertised. Note the bit about installing zip on the Linux remote and, if you already have a connection to the Linux remote in place, you''ll have to delete it and add it back in again. |
Hi,
When i used the headers as tile, the IDE give me error: can not open source file "*.h".
I can't find these header files in my vc dierectory, where is "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\Linux\include\usr\include\x86_64-linux-gnu\sys".
Where i can find these files? I'll appreciate that.
The text was updated successfully, but these errors were encountered: