#3 Give MAP files a meaningful name

[Bill Pedersen]

Currently there is only the option of requesting .MAP's from a LINK via the GNV_LINK_QUALIFIERS. This then ends up creating .MAP files of the form:

.MAP;109

or

baa_432ced.MAP;1
baa_432dfe.MAP;1
baa_432e02.MAP;1

It would be nice, especially when working with large packages like Samba where there are 100s of images if the MAP files could have the name of their image, rather than the name of the option file created during the process.

[Bill Pedersen]

The issue is the LINKER does not appear to take the name from the /EXE= option but from the first file it sees, which in our case ends up being the options file. Here is a command line example:

LINK/MAP=dga8:[listings.samba] -
      /EXEC=REF_ROOT:[samba-4^.3^.1.bin.default.source4.heimdal_build]compile_et. -
      REF_ROOT:[samba-4^.3^.1.bin]baa_46d25e./OPT

Which resulted in the baa_46d25e.MAP file to be crearted in the dga8:[listings.samba] location. Where the map location was created in this case from the GNV_LINK_QUALIFIER environment variable.

.MAP files are created from LINK commands of this nature:

LINK/MAP=dga8:[listings.samba] -
        /SHAR=REF_ROOT:[samba-4^.3^.1.bin.default.lib.replace]libreplace-samba4.so - 
        sys$input:/OPT, -
        $1$DGA8:[gnv_helpers.samba]gnv$libreplace-samba4.opt;/OPT

[John Malmberg]

The map files with the temporary names are a result of the CC wrapper sometimes using generated temporary files to work around limitations in the DCL commands issued to the compiler or other reasons a tempoarty file is used.

I am adding a GNV_LINK_MAP environment variable that when set to 1 for enabled will add a /map=exename.map file to the link command.