Forum Post: ELF format with build app_pe64Pe path embedded into binary file after invoking hex6x

When I build a binary file ( *.b0) from the generated ELF-formatted file using hex6x, I notice a build path is put in the binary.  This is bad because the CRC is calculated over the image.  Every engineer would always need to build to the same folder on his/her hard drive to ensure they had the same image output, to indicate that they are using the same source code (to track issues, test, etc) 

Is there any fix for this without moving to a different toolset?  I don't wish to upgrade Code Composer version and/or tools. 

I remember seeing this regarding the aisGen utility, but I can't find that link nor did it describe the exact toolset we are using. 

Here is the data from the binary file:

¨°à¨ªà¨ª@(#)__ASM__ = C:/some_long_path/app_pe64Pe@(#)__ISA__
= 64P@(#)__PLAT__ = C6457@(#)__TARG__ = ti.targets.elf.C64P_big_endian@(#)__TRDR__ =
ti.targets.omf.elf.Elf32

Thanks,

S.