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
  • Andrew Beckett

    For a start, Save Defaults doesn't load all context files (the Save Defaults is related to .cdsenv files - and it doesn't trigger auto-loading of all the context files as a side effect). Secondly, using find will find all the 64 bit as well as 32-bit context files.

    But most importantly, why on earth would you want to do this? What benefit would it have? 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.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    For a start, Save Defaults doesn't load all context files (the Save Defaults is related to .cdsenv files - and it doesn't trigger auto-loading of all the context files as a side effect). Secondly, using find will find all the 64 bit as well as 32-bit context files.

    But most importantly, why on earth would you want to do this? What benefit would it have? 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.

    Regards,

    Andrew.

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.