Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 16204
  • 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

How to load ALL context files?

tweeks

...through SKILL, not by doing, e.g. Options->Save Defaults and choosing "All Possible Tools".

 

 One cheesy way I can think of is to do:

sh("find $CDSHOME/tools -type f -name \*.cxt > contexts")

Then foreach context file, call loadContext() on it. 

I assume there's a better way......

 

Parents
  • tweeks
    Andrew Beckett said:
    why on earth would you want to do this?

    Well in this case, I'm looking for an undocumented function that will recursively delete a directory. So far I've found artRemoveDirContents(), which very nearly does what I want...

    My theory is that if I load all the functions, I may yet find one that does what I want, buried in a context somewhere. I know Cadence private functions are not intended to be used by customers, but it still saves me time—at least in the short run—to use QA'd Cadence code rather than trying to roll my own from scratch.

    Of course it's not really that difficult to roll a procedure to recursively delete a directory, but I constantly find myself looking for low-level procedures that are not provided in the documented APIs. Sometimes I can find the functionality I want (or at least something closer to it) in the un-documented API....

    Andrew Beckett said:
    For a start, there are some order dependencies between the contexts (such as those which require a parent class which is defined in another context) - so you'll get problems trying to load them in an arbitrary order - you're far better off leaving the auto-load to do its stuff.

    This sounds like a job for getDepends(). Using it, do you think I could reconstruct the context dependency graph, and then load all the (64-bit) contexts in the right sequence? 

      --tom
Reply
  • tweeks
    Andrew Beckett said:
    why on earth would you want to do this?

    Well in this case, I'm looking for an undocumented function that will recursively delete a directory. So far I've found artRemoveDirContents(), which very nearly does what I want...

    My theory is that if I load all the functions, I may yet find one that does what I want, buried in a context somewhere. I know Cadence private functions are not intended to be used by customers, but it still saves me time—at least in the short run—to use QA'd Cadence code rather than trying to roll my own from scratch.

    Of course it's not really that difficult to roll a procedure to recursively delete a directory, but I constantly find myself looking for low-level procedures that are not provided in the documented APIs. Sometimes I can find the functionality I want (or at least something closer to it) in the un-documented API....

    Andrew Beckett said:
    For a start, there are some order dependencies between the contexts (such as those which require a parent class which is defined in another context) - so you'll get problems trying to load them in an arbitrary order - you're far better off leaving the auto-load to do its stuff.

    This sounds like a job for getDepends(). Using it, do you think I could reconstruct the context dependency graph, and then load all the (64-bit) contexts in the right sequence? 

      --tom
Children
No Data

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.