Stats

  • Locked Locked
  • Replies 3
  • Subscribers 165
  • Views 15224
  • Members are here 0
More Content
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

Unable to use tcom package for Active Tcl 8.6 in cadence 17.2 version.

aralex

Hi

The tool OrCAD is not able to recognize the tcom package used by Active Tcl. We are using this in the 16.6 version which uses Active Tcl 8.4 however.

At the command window, when I invoke "package require tcom" the following message is returned

Capture> package require tcom
[ 1]couldn't load library "C:/Cadence/SPB_17.2/tools/lib/tcl8.6/tcom/tcom.dll": invalid argument

But the tcom package contents are present at this location.

Does it have anything to do with 32 bit version of Active Tcl 8.6 ? What is the version of Active Tcl that comes default with 17.2 version. i would like to understand the flow

Thanks

  • oldmouldy
    tcom is almost certainly a 32-bit package which I guess that you have copied into the installation since trying "package require tcom" in the Command Window results in a "package not found" message for my installations. Assuming that you could get the source and necessary tools, you could re-compile tcom for 64-bit but then 64-bit controls would be required by tcom since all of the components running will need to match the 64-bit architecture of the host (Capture) application.
  • aralex
    could you explain how I can re-compile tcom package ? It is a 3.9 version zipped file which I download from the www.vex.net/.../tcom.
    Also what is the Tcl 8.6 version that comes with 17.2 ? I am not clear of the workaround that I need to do.
  • oldmouldy

    Capture 17.2 is a 64-bit application and therefore uses a 64-bit TCL implementation. According to your download link, the download includes a compiled library and source code, which you could compile for 64-bit, with the appropriate tools BUT, even if you do this successfully, the COM capability that you enable will require 64-bit architecture components. Since COM is a long standing Windows 32-bit capability, the chances of finding 64-bit COM components to interact with might be very low, unless you are also building the component for the "other end" of the COM interaction, which seems unlikely from what you have said about COM.

Cadence Guidelines

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.