Subject: Re: ISSUE:DirectC:How to find C/C++ code ???
From: Andrzej Litwiniuk (Andrzej.Litwiniuk@synopsys.com)
Date: Tue Nov 05 2002 - 10:15:54 PST
> This is actually more a question than an issue. Do we need to define how C/C++ code is being found/linked?
>
> -Michael
> n:Rohleder;Michael
> tel;fax:++49-89-92103-680
> tel;work:++49-89-92103-259
> org:Motorola Semiconductor Products Sector;System Design Methodology
1) Same question may be asked for PLI or VPI code.
IMO it should be left to a particular tool how to specify where to look
for C/C++ code, which C/C++ compiler to use or with which libraries to link.
2) Library modules may use external C/C++ code.
Here a library module source code will actually consist of two parts:
its SV part and C/C++ part.
The C/C++ component of a library module may have a form of a source C/C++
code or of an object file, or be a part of a binary library.
Hence some means of associating .c/.cc/.o/.a files with a SV library module
should be provided.
Perhaps the simple file naming convention will do?
The C component of a library module will have the same name (though
with different extension like .c, .cc, .h, .hh, o, .a) as a library module
source file and should be in the same directory (with the exception of
standard C/C++ libraries).
For example, if 'library/foo.v' contains SV source of a library module,
than files 'library/foo.*' [with appropriate extensions] are considered
to be related to that module.
Andrzej
This archive was generated by hypermail 2b28 : Tue Nov 05 2002 - 10:16:29 PST