Re: bug in dbCreateLib / ddCreateLib ??
- From: Trevor Bowen <m27315@xxxxxxxxx>
- Date: Tue, 25 Oct 2005 10:56:56 -0500
That's the problem - the library doesn't exist on that specific machine, so the ddGetObj returns nil, triggering the creation of a new library, which automatically adds the necessary line to the user's cds.lib.
The trick is to delete the library as one of the last steps on the remote job. This will clean up the file space, but more importantly, it will remove the newly added line from your cds.lib file. For example, (plus other enhancements - makeTempFileName() for simple avoidance of name space collision):
tempLibName = nil
unless(ddGetObj("tmpLib")
tempLibName = makeTempFileName("/tmp/tmpLib.")
ddCreateLib("tmpLib" tempLibName)
).....
< close all open cellViews in temp lib ... >
....
when(tempLibName ddDeleteObj(ddGetObj(tempLibName)) )
No bug here - just the need to tidy up behind yourself. ;-)
Sylvio Triebel wrote:
....and I am using lsf (each run is on a different machine...)
Sylvio Triebel wrote:
Hello,
i want to define for each start of icfb a temporary cdb library.
unless( ddGetObj("tmpLib") dbCreateLib( "tmpLib" "/tmp/tmpLib" ) )
So far it works fine, but every start of icfb creates a new line in the cds.lib file.
I could not find anything in SourceLink and just wanted to know, if there is any good trick to avoid the explosion of cds.lib?
Thanks, Sylvio
.
- References:
- bug in dbCreateLib / ddCreateLib ??
- From: Sylvio Triebel
- Re: bug in dbCreateLib / ddCreateLib ??
- From: Sylvio Triebel
- bug in dbCreateLib / ddCreateLib ??
- Prev by Date: Labels in Virtuoso
- Next by Date: Re: Labels in Virtuoso
- Previous by thread: Re: bug in dbCreateLib / ddCreateLib ??
- Next by thread: SKILL for DEF importing
- Index(es):
Relevant Pages
|