05-13-2013 02:53 PM
So my company has an extension written in c built with LabWindows 8 it is an extension for the Tcl scripting language. After I build the application the resulting DLL is dependant on another DLL: tcl84.dll. Also, these lines is generated in the .cws file:
[DLLs Used By Executable 0001]
DLL 0001 = "/C/Tcl/bin/tcl84.dll"
This DLL is not needed by the project as we have several other extensions for Tcl also written in LabWindows that do not have this dependancy. To my surprise however, the other extensions we have for Tcl also have the above line in thier .cws file. Yet the are not listed as a dependency when I examine them with a program like Dependency Walker and the extensions run properly when I remove tcl84.dll from the system.
I have tried deleting the line from the project file and LabWindows simply regenrates it upon my next build. Also, I made an entirely new project carrying over only the .c and .h files and setting up the new project from scratch, but LabWindows still auto-generates those lines when I get my first successful build.
I've included the entire project directory in my post.
Solved! Go to Solution.
05-14-2013 07:41 PM
Does this tcl84.dll interfere with your dll?
http://www.ni.com/white-paper/8911/en
05-15-2013 11:55 AM
@Edna-S wrote:
Does this tcl84.dll interfere with your dll?
http://www.ni.com/white-paper/8911/en
Yes, I need to be able to use this dll with tcl 8.6 but tcl84.dll restricts it to only be used on tcl 8.4.
That link appears to be involved only with the tcl side of things rather than how LabWindows interacts with dlls.
05-15-2013 05:53 PM - edited 05-15-2013 05:54 PM
Solved. Here's a link to my Stack Overflow question with details on the solution: