Arm Community
Site
Search
User
Site
Search
User
Support forums
Arm Development Studio forum
__FILE__ macro
Jump...
Cancel
Locked
Locked
Replies
4 replies
Subscribers
118 subscribers
Views
3582 views
Users
0 members are here
Options
Share
More actions
Cancel
Related
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
over 12 years ago
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
Scott Douglass
over 12 years ago
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?
Cancel
Vote up
0
Vote down
Cancel
Reply
Scott Douglass
over 12 years ago
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?
Cancel
Vote up
0
Vote down
Cancel
Children
No data