( ESNUG 321 Item 1 ) ---------------------------------------------- [6/8/99]
Subject: ( ESNUG 317 #7 ) WARNING! Synopsys Tcl Messes w/ DC_shell Scripts
> Q: If I only want to use DC_shell, do I have to re-write my scripts?
>
> A: No. dc_shell will function the same it did before. You only have to
> worry about converting scripts if you want to use Tcl.
>
> - [ Erich of Synopsys ]
From: Robert Wiegand <rwiegand@mailsrv.ensoniq.com>
John,
There is one subtle exception. The .synopsys_dc.setup file in the
$SYNOPSYS/admin/setup directory MUST be in tcl-s format, as well as any
scripts included from here. I add the following line to the end of the
setup file in the $SYNOPSYS/admin/setup directory:
include synopsys_root + "/admin/setup/.synopsys_dc.setup.global"
I use the global setup file to set up a shared Synopsys cache for all
users, grab information from Unix variables to set library and project root
directory variables for assembling search path strings, set global aliases
and settings across all users and projects, and apply any version specific
bug fix hidden variable workarounds.
I found out about the tcl-s requirement the hard way when I was in the beta
program for this version. It normally takes me about 5 minutes to get an
existing project up and running a new version, but this nasty suprise took
me about 4 hours to get past. Since I had no tcl documentation (is there a
"TCL for Dummies" out there somewhere?), and the conversion utility didn't
support a most of constructs I use (including COMMENTS!), I was left to
hack at it using examples from the PrimeTime documentation as a guide.
Unfortunately, I was not able to continue beta testing since I was in the
middle of several critical mass projects at the time. I hope the script
conversion utility has improved since then.
- Bob Wiegand
Ensoniq, Corp. Malvern, PA
|
|
