Error in $(COBIA_INCLUDE) environment variable

[ahmedsabriz]

Hello,

This is a minor issue but I noticed the $(COBIA_INCLUDE) environment variable in Visual Studio is wrongly defined. When I try to peek into COBIA headers from within my class I get an error "We were unable to open file capeinterfaces_1_2.h. It may have been moved, renamed or deleted.
C:\Users\{username}\AppData\Local\Programs\Common\CAPE-OPEN Laboratories Network\Include\tories Network\Include\capeinterfaces_1_2.h"

Notice how the path seems to be pasted wrongly causing an overlap in it. In any case, I simply removed the variable from additional include library and put the path manually. However, when I uninstalled the COBIA SDK and installed the 1.2.0.6 version, the variable was once again added with the wrong path.

I would like to know if I can correct the variable somehow for the sake of convenience.

[jasper]

I am not clear on this - the value you show is the value of $(COBIA_INCLUDE), including the header file name?

What does

echo %COBIA_INCLUDE%

from a command prompt say?

[ahmedsabriz]

Thank you Dr. Van Baten for your reply. I get C:\Users\{username}\AppData\Local\Programs\Common\CAPE-O~1\Include\. Visual Studio for some reason defines the full path as C:\Users\{username}\AppData\Local\Programs\Common\CAPE-OPEN Laboratories Network\Include\tories Network\Include\. So, the header files do compile, yet peeking at a specific header requires replacing the environment variable with the correct path.

[jasper]

[ahmedsabriz]

Compilation is not affected. All builds are successful. The path is defined correctly until extra characters (last 23 characters to be precise) are repeated which results in error when browsing the dependencies or peeking into the libraries.



I add the path instead of the variable to all additional include directories. I was curious to know if I can edit this environment variable and if this error was caused by something I did.

[Update] I managed to edit and correct the variable.

[jasper]

So this error shows when you select "go to definition" but not during compile? That is strange. This would imply Intellisense it wrong (and not from the environment variable, which is apparently correct).

May I ask how you managed to fix it?

[ahmedsabriz]

I don't believe it only affected intellisense because opening the cobia dependencies from the solution manager resulted in the error same error. I found out I can change the variable by running "rundll32.exe sysdm.cpl,EditEnvironmentVariables" in CMD and substituted
C:\Users\ahmed\AppData\Local\Programs\Common\CAPE-O~1\Include\
to
C:\Users\ahmed\AppData\Local\Programs\Common\CAPE-OPEN Laboratories Network\Include

[jasper]

[ahmedsabriz]

I do see all the include files in command line. I can see how you are suspecting that Visual Studios is parsing the short path incorrectly and it makes sense to me. I am using the latest Visual Studios Community 16.10.2

[jasper]

I cannot reproduce the issue.

I have logged a related item here