• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. What is the difference between the $PATH variables?

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 124
  • Views 6677
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

What is the difference between the $PATH variables?

AndreyVolk
AndreyVolk over 7 years ago

This applies to different instruments, but in the example of SPECTRE.
in bash environment $PATH variable is setting
1)
export MMSIMHOME=$CADHOME/SPECTRE16
export PATH=$PATH:$MMSIMHOME/tools/bin

2)
export MMSIMHOME=$CADHOME/SPECTRE16
export PATH=$PATH:$MMSIMHOME/bin

In both cases, everything seems to work.
But in the first case
.......
lrwxrwxrwx. 1 root root 22 Aug 15 11:12 spectre -> ../spectre/bin/spectre
lrwxrwxrwx. 1 root root 30 Aug 15 11:12 spectre_encrypt -> ../spectre/bin/spectre_encrypt
lrwxrwxrwx. 1 root root 27 Aug 15 11:12 spectre_root -> ../spectre/bin/spectre_root
lrwxrwxrwx. 1 root root 21 Aug 15 11:12 spectremdl -> ../mdl/bin/spectremdl
lrwxrwxrwx. 1 root root 28 Aug 15 11:12 spectreserver -> ../spectre/bin/spectreserver
lrwxrwxrwx. 1 root root 22 Aug 15 11:12 spfchecker -> ../emir/bin/spfchecker
lrwxrwxrwx. 1 root root 22 Aug 15 11:12 spicevisionpro -> ../SpiceVision/wrapper
lrwxrwxrwx. 1 root root 19 Aug 15 11:12 sptr -> ../spectre/bin/sptr
lrwxrwxrwx. 1 root root 21 Aug 15 11:12 tbl2macro -> ../emir/bin/tbl2macro
lrwxrwxrwx. 1 root root 20 Aug 15 11:12 temir -> ../spectre/bin/temir
lrwxrwxrwx. 1 root root 24 Aug 15 11:12 ultrasim -> ../ultrasim/bin/ultrasim
lrwxrwxrwx. 1 root root 26 Aug 15 11:12 ultrasim32 -> ../ultrasim/bin/ultrasim32
lrwxrwxrwx. 1 root root 26 Aug 15 11:12 ultrasim64 -> ../ultrasim/bin/ultrasim64
lrwxrwxrwx. 1 root root 24 Aug 15 11:12 uricheck -> ../relxpert/bin/uricheck
lrwxrwxrwx. 1 root root 24 Aug 15 11:12 usimEmirUtil -> ../emir/bin/usimEmirUtil
lrwxrwxrwx. 1 root root 26 Aug 15 11:12 usimEmirUtil32 -> ../emir/bin/usimEmirUtil32
lrwxrwxrwx. 1 root root 26 Aug 15 11:12 usimEmirUtil64 -> ../emir/bin/usimEmirUtil64
lrwxrwxrwx. 1 root root 27 Aug 15 11:12 usimtap2pti -> ../ultrasim/bin/usimtap2pti
lrwxrwxrwx. 1 root root 29 Aug 15 11:12 usimtap2pti32 -> ../ultrasim/bin/usimtap2pti32
lrwxrwxrwx. 1 root root 29 Aug 15 11:12 usimtap2pti64 -> ../ultrasim/bin/usimtap2pti64
lrwxrwxrwx. 1 root root 18 Aug 15 11:12 xps -> ../spectre/bin/xps
lrwxrwxrwx. 1 root root 19 Aug 15 11:12 xpss -> ../spectre/bin/xpss

In the second case, this is a link to only one file.
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 spectre -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 spectre_encrypt -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 spectre_root -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 spectremdl -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 spectreserver -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 spfchecker -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 spicevisionpro -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 sptr -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 28 Aug 15 11:12 srrversion -> ../share/dfII/bin/srrversion
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 tbl2macro -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 temir -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 ultrasim -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 ultrasim32 -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 ultrasim64 -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 uricheck -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 usimEmirUtil -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 usimEmirUtil32 -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 usimEmirUtil64 -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 usimtap2pti -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 usimtap2pti32 -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 usimtap2pti64 -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 xps -> .cdnWrapperIndep
lrwxrwxrwx. 1 root root 16 Aug 15 11:12 xpss -> .cdnWrapperIndep

Which setting is more correct?

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    I freed your post from moderation (lots of repeated words in the directory listing caused the system to think it was spam, which it isn't).

    You should be able to use either. Historically there was no consistency in the path settings between different release streams, but we've been gradually standardising on the <instDir>/bin approach.

    Don't worry about what the links go to - the common wrapper knows how it's been called. so will work in either case.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • AndreyVolk
    AndreyVolk over 7 years ago in reply to Andrew Beckett

    Thanks for the answer.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information