• Locked Locked
  • Replies 4 replies
  • Subscribers 119 subscribers
  • Views 3496 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
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

__FILE__ macro

Steven Logan
Note: This was originally posted on 8th May 2013 at http://forums.arm.com

When using the __FILE__ macro in RVDS4, it only expands to "source/file.cpp". It won't ever expand to more than just the directory the file is in.
It seems everyone has problems shortening the path from __FILE__ rather than getting it to show more.

Is there anyway to resolve this?

Loggie
Parents
  • Arm Employee Badge
    Note: This was originally posted on 8th May 2013 at http://forums.arm.com

    I would expect that __FILE__ was the same as the file name given on the command line.  (Or for #included files, the path constructed from the parent directory of a file on the command line and/or the -I directives.).

    Can you get what you want by specifying longer paths on the command line?
Reply
  • Arm Employee Badge
    Note: This was originally posted on 8th May 2013 at http://forums.arm.com

    I would expect that __FILE__ was the same as the file name given on the command line.  (Or for #included files, the path constructed from the parent directory of a file on the command line and/or the -I directives.).

    Can you get what you want by specifying longer paths on the command line?
Children
No data