Bugzilla – Full Text Bug Listing
| Summary: | Scanner Discovery should allow environment or build variables | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Gavin S <gavinswanson> |
| Component: | cdt-build | Assignee: | cdt-build-inbox <cdt-build-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | Andrew Gvozdev <angvoz.dev> |
| Severity: | normal | ||
| Priority: | P3 | CC: | cdtdoug, eclipse, yevshif, zeratul976 |
| Version: | 8.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
Do you need variable to point to the compiler or to the specs file? (In reply to comment #1) > Do you need variable to point to the compiler or to the specs file? For the compiler. This functionality is useful for a shared project where individuals may have things installed in a common sub-folder of some definable environment variable such as $HOME. As I need to use different and occasionally changing compilers in my various projects and targets I would like to set prefix and suffix for the compiler. So once I need a different version I simply would change the suffix/prefix instead of nearly 100 projects.
Example win32:
prefix: i686-gnu-cygwin-
suffix: -4.3.2
${prefix}gnu${suffix}
==> i686-gnu-cygwin-gcc-4.3.2
And removing the two variables for linux builds enables the standard compiler.
(In reply to Gavin S from comment #0) > 2.Try setting the Discovery Command to use $HOME/, ${env_var:HOME}/, or ~/ Where in the UI are you setting this "Discovery Command"? |
Build Identifier: 20110615-0604 The Scanner Discovery command line does not allow the use of build, or environment variables. Using ~ to get the home directory of the user is also not available. Reproducible: Always Steps to Reproduce: 1.Start project 2.Try setting the Discovery Command to use $HOME/, ${env_var:HOME}/, or ~/ 3.Fail