Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 Environment variables in include paths
 New Topic  Topic Locked
 Printer Friendly
Author Previous Topic Topic Next Topic  

diarrhio
Ketchup Master

53 Posts

Posted - Jan 19 2005 :  2:33:32 PM  Show Profile
I've encountered an issue with VAX not parsing symbols in directories designated through an environment variable. For instance, if, in the "Additional include directories" box in the project settings window I enter:

$(QTDIR)/include

VAX will not parse those symbols. However, if I use the standard nomenclature of:

d:\\qt\\3.3.3\\include
or
..\\..\\qt\\3.3.3\\include

VAX will parse that directory just fine. It would be *very* nice if VAX could support this type of nomenclature. It's much easier to switch the qt directory in one place (i.e in the environment variable) than having to open each configuration of each project just to get VAX to recognize the symbols in a directory.

Thanks.

support
Whole Tomato Software

5566 Posts

Posted - Jan 21 2005 :  12:35:13 PM  Show Profile
Something broke. VA X should recognize $(env) in the IDE settings.

For now, add $(QTDIR)\\include to Tools|Options|Projects|VC++ Directories|Include files. No need to modify the project and no need to resort to hardcoded paths.

case=492
Go to Top of Page

diarrhio
Ketchup Master

53 Posts

Posted - Jan 22 2005 :  03:56:37 AM  Show Profile
Cool. Thanks for the reply.

D
Go to Top of Page

Baga
Tomato Guru

122 Posts

Posted - Jan 23 2005 :  2:44:30 PM  Show Profile
Maybe it was working/using %QTDIR% form?
Go to Top of Page

schoenherr
Tomato Guru

Germany
160 Posts

Posted - Jan 24 2005 :  02:07:32 AM  Show Profile
using msdev 6.0 and VAX 10.1 build 1293 such include settings work well.
90% of our include directives are constructed with $(...) statements.
Go to Top of Page

diarrhio
Ketchup Master

53 Posts

Posted - Jan 24 2005 :  02:33:08 AM  Show Profile
Hmmmm. I guess I was using an older version (1289). Seems to work fine now using 1293. Sorry for the alarm.
Go to Top of Page

support
Whole Tomato Software

5566 Posts

Posted - Jan 29 2005 :  11:09:48 AM  Show Profile
The problem appears to be with projects migrated from VC6. -?The additionalIncludeDirs list is delimited with commas. -?In vs.net they are supposed to be semi-colons. -?When a project is migrated, the commas don't get changed. -?But if you use the vsnet "add additional include dir" dialog in a project, then it converts the commas to semi-colons and all of a sudden VA X can read the setting.

We will work around the nuance in our next build.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Topic Locked
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000