• 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 SKILL
  3. Problem with running a c program via Cadence

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13515
  • 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

Problem with running a c program via Cadence

useratcad
useratcad over 16 years ago

Hello,

I'm trying to run a program located at ~/src/prog/myprog written in Cpp.

But when I want to start it with
ipcBeginProcess("~/src/prog/myprog") it won't work.

Cadence says:
sh: ~/src/prog/myprog: not found

What is the problem here?

A complete path will work, but I need the short one, like above.

And another question: What is the best way to run commands? Via ipcBeginProcess, sh or internal functions like (CreateDir. DeleteDir, ...)
ipcBeginProcess("mkdir -p test")

CreateDir ("test")

sh("mkdir -p test")

 

Thanks Tim 

  • Cancel
  • skillUser
    skillUser over 16 years ago

     Hi Tim,

    You can use "simplifyFilename()" to expand a file name to a fully qualified path, for example:

     

    ipcBeginProcess(simplifyFilename("~/src/prog/myprog"))

    For your question about which is best, it really depends on what you need to do; if bi-directional communication is required between DFII and the external program, then use the ipc* functions, but if you just need to fire off an external command and don't need any further interaction with it, use one of the csh(), sh(), shell() or system() commands.

    Hope this answers your questions!

    Regards,

    Lawrence.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • useratcad
    useratcad over 16 years ago

    great! Thanks for the reply. That helped a lot! 

    • 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