Using the Waveform Access Library (WAL)

Hi all,

I need to use the WAL to extract data from a simulation run.

However, I fail to even get started with the "hello world" example from
chapter 11 of the OSS reference: I installed all of IC5141 but still
haven't got a
voCompiler.h or virtuos.a (BTW that name is spelled both virtous.a and
virtuos.a in the OSS ref).
I managed to get away without voCompiler.h, but now linking fails with
an
"undefined reference to `voCopyString'".

Do I need to install any other component for these files?

Nadine

 

[Erik Wanta]

What is WAL? Which tools uses it? Does Cadence recommend using it?
---
Erik

 

Hi David,

David Cuthbert wrote:

Nadine@MailSys.de wrote:
I need to use the WAL to extract data from a simulation run.

However, I fail to even get started with the "hello world" example
from
chapter 11 of the OSS reference: I installed all of IC5141 but
still
haven't got a
voCompiler.h or virtuos.a (BTW that name is spelled both virtous.a
and
virtuos.a in the OSS ref).
I managed to get away without voCompiler.h, but now linking fails
with
an
"undefined reference to `voCopyString'".

Do I need to install any other component for these files?

Hm... looks like there are packaging and/or documentation bugs here.

voCompiler.h is a trivial header which just defines CDS_BEGIN_FUNCS
and
CDS_END_FUNCS as (I'm doing this from memory):
[...]

I don't see a virtuos.a in the IC5.1.41 install, either; however, you

should be able to use libvirtuos_sh.so in tools/lib. When linking
your
executable, add:
-L$CDS_INST_DIR/tools/lib -lvirtuos_sh
to the end and it should (hopefully) work.

[...]

Thank you for this information. I was able to compile the example this
way.
I had to link the wal.a into a dynamic library and use dlopen to access
it
on a non-RH7.2 box due to references to errno and __ctype_b, but that
was
expected and not a big deal. It works just fine now.

Thanks
Nadine

 

Andrew Beckett wrote:

I'd say WSF is pretty much obsolete, and would not recommend anyone
starting
any new developments based on it. Note, this is a personal opinion -
I've not
checked internally for an official viewpoint on this.

That's a pity to hear. To my knowledge (from searching the web) it is
only
WSF and the nutmeg format that are both accessible from C and supported
by spectre. I really would hate having to go through Ocean (including
all the overhead of spawning the process, feeding it the right
commands, converting the
data to ASCII and back, propably leading to a loss of precision) just
to read the simulation data.

A few years ago you mentioned that a package "SRR" would one day be
available to read PSF:
http://groups.google.com/groups?hl=de&lr=&ie=UTF-8&selm=9osvsu05jojtiabore3hm6jhiasut4p4p0%404ax.com
Any news on this? (BTW: Where can I search for a PCR number on the new
sourcelink home?)

Nadine