Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 15324
  • 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

Passing skill variable to shell command

GDCRA

Hi,

I want to run perl excecutable from skill procedure. I have my design name in  variable mycell, library name in mylib and runpath in myrunpath variable.

I am running following way

CommandLine="netlistextract -library mylib -design mycell  -rundir myrunpath"

cid=ipcBeginProcess(CommandLine)

Looks like skill variable are not getting evaluated when i do CommandLine. How do I fix it ?

Is there elegant way to do what I am trying to do here ?

Thanks

GC

  • skillUser

    Hi GC,

    You can build the 'CommandLine' variable using sprintf() (or strcat, depending on your inputs or preferences), for example:

    sprintf(CommandLine "netlistextract -library %s -design %s -rundir %s" mylib mycell myrunpath)
    cid = ipcBeginProcess(CommandLine)

    Best regards,

    Lawrence.

  • GDCRA
    in reply to skillUser

    Thanks Lawrence. That worked like charm. Is there way I can monitor output of above command in CIW ?

    I was using ipcReadProcess(cid) but I need to enter this line multiple time. 

    Thanks

    GC

  • skillUser
    in reply to GDCRA

    Hi GC,

    Your best bet is probably to convert the code into an 'asynchronous' IPC (inter-process communication) call so that whenever 'data' is present on the channel (i.e. the external script has printed something) you can deal with it. There should be examples and solution articles for asynchronous IPC on the Support website as well as in the documentation.  If you don't want to do that you could set up a while() loop, like while(ipcReadProcess(cid) ... or while(ipcIsAliveProcess(cid) ... 

    Best regards,

    Lawrence.

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.