Comments on: Getting subversion and Cadence to play nice together

By: profiles.google.com/trustmeiman…

profiles.google.com/trustmeiman… — Wed, 07 Sep 2011 12:13:21 +0000

Great set of scripts.

How will the updated subversion 1.7 working copy format influence this? Presumably many of the issues will be resolved since we won’t have .svn directories all over the place any more.

Kind regards,
Richard.

By: Steven

Steven — Mon, 17 Aug 2009 11:26:48 +0000

You just need to make sure that the cdsLibMgr.il is located in the directory where you start-up icfb. First time I was able to find some useful info on the cdsdoc: Cadence Library Manager User Guide. The setup.loc file defined the different paths where the cdsLibMgr.il is being searched:
————————————————————–
The file is loaded from the first location in the order defined in the Cadence setup search file (setup.loc) as described in Cadence Application Infrastructure User Guide. The typical order used to load this file is

* The current working directory
* The home directory
* The your_install_dir/share file

When a file is found from one of these locations, the file is loaded and the search stops.

You can customize the name for the cdsLibMgr.il file using a default setting in your .cdsenv file. For a detailed description of this setting, see “Using UNIX to Add Settings to the .cdsenv File”.
————————————————————–
This did the trick for me.

By: Poojan Wagh

Poojan Wagh — Fri, 27 Feb 2009 20:39:22 +0000

@VirtualCLD:
Hmm… that is very odd. The library manager and schematic menus are loaded using different methods. It’s weird that both of them are broken.
Could you try (as a debugging step) setting things up without the cdsvn sub-directory?
Also, can you try calling any of the functions defined in the scripts, to see if they are defined?

P.S. Sorry for the late response.

By: VirtualCLD

VirtualCLD — Tue, 03 Feb 2009 22:03:26 +0000

Thanks for the quick response. Unfortunately, I’ve tried placing the cdsvn directory below the working directory, while keeping the menu/ subdirectory in the Cadence working (start) dir, and editing the .cdsinit files. However, I still can’t seem to get the SVN menu options in the Library Manager or Schematic Editors. Maybe I have to modify the SKILL scripts with the new directory paths?

By: Poojan Wagh

Poojan Wagh — Thu, 29 Jan 2009 00:42:15 +0000

Hi, VirtualCLD. The scripts should work when you move them to a subdirectory (provided you change your .cdsinit files). However, the menu definitions are different. Cadence looks for menu additions in the menu/ subdirectory of the Cadence start directory. So, those have to be collocated.

By: VirtualCLD

VirtualCLD — Tue, 27 Jan 2009 18:32:10 +0000

This is a great resource as I’ve just started to learn the headaches of using Cadence projects with subversion. I had two questions related to your scripts.

1) I see that if I extract the tar file, I get a CDSVN directory. I then can go into CDSVN and use THAT directory as my working directory. I could also copy the entire contents of CDSVN and paste it into my current icfb working directory and then edit the .cdsinit file from there. However, I would like to have the scripts all live in a sub-dir like this icfb_work_dir/cdsvn/ I would run icfb within icfb_work_dir, but the SKILL scripts would reside in the sub-dir ./cdsvn Unfortunately, when I do this, I can’t get the scripts to load properly and I no longer have the menu hooks. I realize this is purely an aesthetic/organizational request, but if you know how I could do this, I would greatly appreciate it.

2) I see the SVN copy commands in LibManager, but they seems to be basic Cell/View copy commands. They do not appear to support Hierarchical copying. Manually copying a singe Cell or View with svn copy from the console isn’t too bad, but where Cadence’s copy command is extremely useful is when you need to copy an entire hierarchy that consists of dozens of Cells (and there corresponding views). Is there a way to get Hierarchical Copying to work with your scripts, or would this require some advanced SKILL scripting (my SKILL knowledge pretty much zero)?

By: Poojan Wagh

Poojan Wagh — Thu, 23 Oct 2008 11:54:43 +0000

@Dariusz:
I didn’t realize that the lock command arrived in subversion 1.4. Indeed, 1.3 is the version that ships with Red Hat Enterprise Linux–which most Cadence users are using. Thanks for posting the solution! Glad to hear it worked.

By: Dariusz

Dariusz — Thu, 23 Oct 2008 09:10:31 +0000

Hi,

I have found the problem. This is the subversion version number. I updated to 1.4 and everything works perfectly. Thanks once again for a great job.
Dariusz

By: Dariusz

Dariusz — Wed, 22 Oct 2008 07:58:51 +0000

Hi Poojan,
great work. Thanks for this extremelly useful scripts.
However, I am experiencing some issues with locking. When I did it through the popup menu
the error message appears, since the svn does not understand command lock.
I tried to solve the issue by replacing “svn lock” in your locking script to just “lock”,
as the lock command exists in /bin directory. Unfortunately, it does not solve the problem,
since some data incompatibilities are pointed out.
Therefore I would like to ask you if the way I choose is correct. Maybe the reason of my troubles is totally different.

Kind regards
Dariusz

By: Pictorial introduction to using Cadence & Subversion

Pictorial introduction to using Cadence & Subversion — Fri, 05 Sep 2008 12:24:36 +0000

[...] I previously blogged about some scripts I use to help Cadence & Subversion be more compatible. I received some feedback that the scripts were incomplete and came without any usage model. So, I went through an excercise to document the scripts and to make sure they were complete. [...]