Handling of VerilogA Views

[Guenther Sohler]

In our setup I have written an alternative copy script,
which copies views hierarchically into a release library and also
does the referencing correctly. This works fine, If I handle views like
symbol, schematic,layout,abstract ...
But it does not work for veriloga views(they are different in nature)

during normal copying i use
dbOpenCellViewByType
v
dbID
v
dbCopyCellViewByType

these do not work for verilog a views because dbOpenCellViewByType
cannot generate a dbID for them.
Is there also a way to get a dbID for a veriloga
view(its actually a file containing a veriloga behavioural description)


rds

 

[Andrew Beckett]

On Wed, 08 Jun 2005 09:23:32 +0200, Guenther Sohler
<guenther.sohler@newlogic.com> wrote:

In our setup I have written an alternative copy script,
which copies views hierarchically into a release library and also
does the referencing correctly. This works fine, If I handle views like
symbol, schematic,layout,abstract ...
But it does not work for veriloga views(they are different in nature)

during normal copying i use
dbOpenCellViewByType
v
dbID
v
dbCopyCellViewByType

these do not work for verilog a views because dbOpenCellViewByType
cannot generate a dbID for them.
Is there also a way to get a dbID for a veriloga
view(its actually a file containing a veriloga behavioural description)


rds

You should use the ccpCopy() function to copy things in general - this will
cope with non-CDB views. The db functions are only for CDB (and OA) views.

Regards,

Andrew.