• Garett Bass (11/11) Dec 23 2005 I really hate having non-source file pollution in my source directory.
• Chris Lajoie (5/16) Dec 23 2005 Even if I'm using build I always have a batch file I use to compile. I

"Garett Bass" <garettbass studiotekne.com> writes:

I really hate having non-source file pollution in my source directory.

Everytime I compile a D program, I wind up with a .map file in my source 
directory.  I've successfully sent my binary and object files to other 
directories, but I can't figure out how to relocate the .map file.

I suspect the .map file is generated by the linker, so I tried to find a 
linker flag that would either relocate or drop the .map file.  So far I 
haven't found such a flag.

BTW, what is the .map file?  Maybe I'll just hack Build to delete or 
relocate it.

Thanks,
Garett 

Chris Lajoie <ctlajoie yahoo.com> writes:

I really hate having non-source file pollution in my source directory.

Everytime I compile a D program, I wind up with a .map file in my 
source directory.  I've successfully sent my binary and object files to 
other directories, but I can't figure out how to relocate the .map file.

I suspect the .map file is generated by the linker, so I tried to find 
a linker flag that would either relocate or drop the .map file.  So far 
I haven't found such a flag.

BTW, what is the .map file?  Maybe I'll just hack Build to delete or 
relocate it.

Thanks,
Garett

Even if I'm using build I always have a batch file I use to compile. I
do this because I don't want to type out the args, but this also lets me
add other commands like del *.map and del *.obj (because '-o-' crashes
dmd sometimes)
Chris