This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Environment variables

How do I use system environment variables to specify a path to a source file?

Parents
  • "but beyond that it is worthless"

    I wouldn't go as far as "worthless," but uVision's Project management facilities certainly do have serious limitations - as I have mentioned on this forum several times before; eg

    * There is no way to specify options common to more than one Target;

    * It is not possible to re-order the Groups within a Project.
    This one is unforgivable, as the order of things within a Project defines the order in which they're done!

    * There is no way to specify dependencies for Custom Translators - it's just "Always Build" or "Never Build".
    It would be useful if there was at least the option to right-click a file or Group and choose to rebuild (translate) that item - currently, if you've unchecked 'Include in Build' you can't even "manually" trigger a rebuild of the item :-(

Reply
  • "but beyond that it is worthless"

    I wouldn't go as far as "worthless," but uVision's Project management facilities certainly do have serious limitations - as I have mentioned on this forum several times before; eg

    * There is no way to specify options common to more than one Target;

    * It is not possible to re-order the Groups within a Project.
    This one is unforgivable, as the order of things within a Project defines the order in which they're done!

    * There is no way to specify dependencies for Custom Translators - it's just "Always Build" or "Never Build".
    It would be useful if there was at least the option to right-click a file or Group and choose to rebuild (translate) that item - currently, if you've unchecked 'Include in Build' you can't even "manually" trigger a rebuild of the item :-(

Children