Conference clt::mms

1379.0. "How to determine which system headers are included in a C program" by CSC32::E_VAETH (Suffering from temporary brain cramp, stay tuned) Mon Mar 24 1997 11:28

Hi,

OpenVMS Alpha V6.2 and MMS.

Notes 640 and 1166 are related to this question, however since those notes are
old, I thought I'd start a new one.  Based on those notes, there isn't any easy
way to determine what system header (.H) files are used in the compilation. 

Will this functionality be added to MMS?

Is there an easier way to determine what header file is included?  For example
the CC/MMS qualifier to find out what the include modules are.  His output looks
like this:

   A.OBJ : DKB500:[E_VAETH]A.C  
   A.OBJ : SYS$COMMON:[SYSLIB]DECC$RTLDEF.TLB

The customer would like to see:

   A.OBJ : SYS$COMMON:[SYSLIB]DECC$RTLDEF.TLB(STRING=STRING.H)

Shouldn't the references to the DECC library include the name of the
module?  

If that isn't the case, then is there an alternative way to determine what
system header (.H) files  are used in the compilation besides what is listed in
notes 660 and 1166?  That information has already been passed to the customer
and the customer feels that suggestion is not very useful.  The complaint is
that the CC/MMS command does not give him the information about which system
headers are used by his program.  If he doesn't know which files to put in the
MMS description file, he cannot do anything appropriate with them.

Thanks,

elin

    Hi Elin,
    
    With respect to the general question of how to determine which header
    files are actually included, CC/LIST/SHOW=INCLUDE will add that
    information the page header of the list file (provided that the include
    file actually spans a full page). However, I don't know of any reliable
    automated way to capture this information for use in an MMS dependency
    unless you want to parse the list file.
    
    I agree that the output of CC/MMS should probably be a dependency based
    upon the module within the library and not the library itself. You may
    wish to take this up with the DEC C group, as the dependencies are
    actually generated by the C compiler and not MMS.
    
    The only way that I can think of for MMS to determine specific
    information on include files would be to enhance the description file
    generator (MMS/GENERATE) to search for this information. However, my
    feeling is that this is beyond the scope of the generator because this
    information is very sensitive to the version of the compiler used, not
    to mention that relatively similar support would need to be added for
    other language compilers. This information is best left in the realm of
    the compilers.
    
    -- Daryl

    Thank you for the great explanation.
    
    -elin