linked cds.lib issue!

Discussion in 'Cadence' started by Manju Arasaiah, Jun 16, 2004.

  1. Hi,

    We have a group project where individual users
    have different work-areas to launch icfb from.
    We have a central cds.lib where each user's
    workarea has a link to it so that each user will
    see the same libraries as every other user.
    i.e., the dir structure is something like below:

    /home/project
    /home/project/cds.lib
    /home/project/user1
    /home/project/user1/cds.lib -> ../cds.lib
    /home/project/user2
    /home/project/user2/cds.lib -> ../cds.lib

    Now, when a user creates a new library, Cadence
    (5.0.32) is CONVERTING the link to a file and the
    cds.lib will be copied to the user's directory
    with an entry to the new library added to it.
    This is killing the purpose of each user should
    be able to access every other user's libraries.

    Is there a reason why Cadence can not add the new
    library entry to a "linked cds.lib" file?

    I really appreciate your quick
    workaround/solution if one can suggest.


    thanks, Manju
     
    Manju Arasaiah, Jun 16, 2004
    #1
  2. Manju Arasaiah

    Erik Wanta Guest

    Roger:
    SOFTINCLUDE whatever/cds.lib
    ---
    Erik


     
    Erik Wanta, Jun 17, 2004
    #2
  3. This does not solve his problem. If user1 makes new library, there is no way
    that user2 sees it.

    My opinion is that the best is to arrange common design area. Each user can
    protect his files by setting the permission for his library to be read only.
    And of course each of them can keep his files in his home directory, so he
    can also limit the access to the files themselves.

    Hristo
     
    Hristo Brachkov, Jun 17, 2004
    #3
  4. Hi,

    we have nearly the same environment and also work
    with a central cds.lib file, but without links
    rather than I force the tools to find the cds.lib
    at the central location with the following SKILL
    code in the .cdsinit.

    ;; forcing cds.lib file path for all updates/creates

    ddSetForcedLib( strcat( t_projectDir "/cds.lib" ) )
    ddUpdateLibList( )

    where t_projectDir in your case has to be /home/project


    Hope this helps.

    Bernd
     
    Bernd Fischer, Jun 17, 2004
    #4
  5. That's exactly what I was going to suggest!

    BTW, the reason for the "problem" is that we don't modify the file in
    place, but rather write a new file to the side and move it in place (I think).
    This is done to prevent the file getting lost if the disk fills up - if you just
    overwrote the file, and then something else caused the disk to fill up in
    the meantime, you might lose the contents.

    The downside of course is that links get trampled on.

    Andrew.
     
    Andrew Beckett, Jun 17, 2004
    #5
  6. Thanks for the msgs so far.

    The requirements are:

    1. Each user should see each others libraries (new as well as existing
    libraries)

    2. The common libraries (sheets_lib, analogLib etc) should loaded only
    once
    per session. If I load a common libraries and the next user also loads
    common libraries (in their respective cds.lib), when he loads my
    cds.lib, he will get to load the common libraries again (kind of
    recursive loading!) which Cadence doesn't like and gives bunch of
    warnings.

    WONDERING about any SKILL command is there to load the cds.lib thru
    ..cdsinit file?

    Having a DM solves this problem???

    thanks for your time,
    Manju
     
    Manju Arasaiah, Jun 17, 2004
    #6
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.