Hi, Chris,

The variables in the System Builder search paths are built-in and do not use
the shell-like ${...} notation.  However, I think that mkxfs (used by System
Builder under the hood) may understand environment variables if you use the
${...} syntax in your search path.  Try it.  Just don't use variables having
the same name as built-in variables (e.g., VARIANT, CPU)

Note that if this works (I haven't tried it) it will *only* work when
performing a build, because it would be mkxfs that expands the variables.
The System Builder user editor will not expand them, so certain searching
and validation operations in the editor will not work.

HTH,

Christian



On 10-09-15 10:09 AM, "Christopher Cope" <community-noreply@qnx.com> wrote:

> Hello,
> 
> Is it possible to use environment variables when adding a search path in the
> system builder?
> 
> We have our system builder project stored in a dynamic clearcase view and not
> all developers use the same drive letter.  Normally we would reference an
> environment variable called VIEW_DRIVE but I can't seem to get this to work.
> 
> Thanks in advance,
> Chris
> 
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post67412
> 

-- 
Christian W. Damus
Software Developer, IDE Team
QNX Software Systems <http://www.qnx.com/>;