Build started: Project: Services, Configuration: Debug VisualGDB. One possible cause for this would be CMakeLists.txt using the regular /path/on/target syntax to specify include directories instead of $ Sorry, it’s hard to suggest anything specific without knowing more details (how exactly is the target declared, what is the current directory with the header file and exactly is is spelled in the Makefile, what exactly gets edited in the CMakeLists.txt file). This topic was modified 3 years, 9 months ago by nOlander.
#Cmake include remote header professional#
Where should I be looking in my configuration to resolve this? I’m using a CMake project that I imported from an already existing CMake project that I had manually created on Visual Studio 2017 Professional with VisualGDB Custom 5.4R12. It also compiles correctly if I copy the header files from usr/local/include to /usr/include, but I don’t intend on doing that on the remote system and I feel like this should be configurable without having to manually adjust the sysroot. Interestingly, the Clang autocomplete works fine with those headers, it just appears that the build is not properly including the usr/local/include folder in the sysroot. I’ve synchronized the sysroot from the Raspberry Pi successfully, and I know the header files are present in the local sysroot, but I can’t get Visual Studio to compile, it just reports Error snap7.h: No such file or directory for whatever header it is unable to find. I have been using VisualGDB for a bit to cross-compile a project for a Raspberry Pi.
0 kommentar(er)
