AnsweredAssumed Answered

How to prevent full path from appearing in binaries?

Question asked by dave408 on Nov 22, 2015
Latest reply on Nov 30, 2015 by dave408

I'm using KDS 3.0 and am wondering why two binaries built from the same revision of source on identically (or so I think) installations of KDS result in different information in the binaries.

 

One thing that is very clear is that full paths are present in the binaries built using my release configuration, which is essentially the same as my debug configuration, but debug information is set to "None".

 

The only thing I have been able to come up with is that the __FILE__ macro generates a full path to the file, rather than the "short" path that takes the include folders into account.

 

Can anyone suggest a way to resolve this?

 

EDIT -- I just saw a post on StackOverflow where IAR added a --no_path_in_file_macros compiler flag to avoid this problem.  Does anyone know of an equivalent for gcc that has worked for you?  I'm currently looking that up now.  http://stackoverflow.com/questions/8487986/file-macro-shows-full-path

Outcomes