Stats

  • Locked Locked
  • Replies 6
  • Subscribers 92
  • Views 14510
  • 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

TCL

Brian Harrison

Hello,

Is there a proper way to load a dynamically loadable TCL extension in encounter?

example:  www.swig.org/tutorial.html

When I complile the above example and try to load it within encounter I get:

couldn't load file "./example.so": ./example.so: cannot open shared object file: No such file or directory

This works fine within a normal tcl shell.

On a previous project I wrote crude placement algorithm in TCL using encounter commands.  This was done to overcome limitations with encounter clock tree synthesis with IBM ASIC methodology.   The algorithm worked great, but was slow since being in TCL.   I could speed this up in C/C++ using SWIG to create the TCL wrapper.  

Any help?

Best Regards,

Brian

 

Parents

  • Thanks JG,

    I'm using the 'load' to load the binary extension.

    The tcl interpreter can be compiled to not to allow dynamic loading,  'load', so maybe that's the problem.

    I tried adding a directory:   set auto_path [linsert $auto_path 0 /home/bharris/dev/swig]

    but no luck. 

    info library gives me:

    /apps/SOC81/08.10.002/share/tcltools/icd8.4.11/lib/tcl8.4

    Is there a way to add a path to it?

     

     

     

    Best Regrads,

    Brian

     

Reply

  • Thanks JG,

    I'm using the 'load' to load the binary extension.

    The tcl interpreter can be compiled to not to allow dynamic loading,  'load', so maybe that's the problem.

    I tried adding a directory:   set auto_path [linsert $auto_path 0 /home/bharris/dev/swig]

    but no luck. 

    info library gives me:

    /apps/SOC81/08.10.002/share/tcltools/icd8.4.11/lib/tcl8.4

    Is there a way to add a path to it?

     

     

     

    Best Regrads,

    Brian

     

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.