Problem in loading .dll built in VC++.NET

[sjhao]

Hi,

I have problem in loading a Tcl extension (.dll) that was build in VC++.NET. The error is: "Could not load "C:/test/newCmd.dll" this library or a dependency library could not be found in library path"

Has anyone met this problem before?

Thanks advance for your help!

Susan

 

[Bong]

It sounds like there might be another DLL that VC++ assumed would be available. Does VC++ tell you anything about external references?

_________________
Bob Rashkin
rrashkin@csc.com

 

[sjhao]

Bong,

Thank you so much for your reply!

Yes, there is another DLL that was used when the newCmd.dll was built. VC++ does list any external dependency. when I use the newCmd.dll on the same computer where it was built, there is no problem, all new command are working. BUT, if I copy the newCmd.dll to aother computer and load the newCmd.dll from a Tcl script in that computer, I got the error "C:/test/newCmd.dll" this library or a dependency library could not be found in library path"

So the problem is why the newCmd.dll can be loaded from the same computer where it was built, but not from other computers?

I built this .dll in Debug mode, not release mode. I tried to build the .dll in release mode, but I got error:" fatal error C1083: Cannot open include file: 'C:\Tcl\include': Permission denied." I do not get the error if I build in Debug mode.

Thanks for your help!
Susan

 

[sjhao]

Sorry, There is a typo in my previous reply:
"VC++ does list any external dependency." should be "VC++ does NOT list any external dependency."

-Susan

 

[Bong]

Well, I'm out of my depth here. I have never used any C++ libraries. Do you know about the Tclrs Wiki (

http://mini.net/tcl/)?

Maybe this page has information you can use:

http://mini.net/tcl/2419

good luck.

_________________
Bob Rashkin
rrashkin@csc.com

 

[sjhao]

Bong,

Thanks for your help! I think that the solution should be related to how to package the DLL that Tcl script can use " package require XXXX ", but I do not know how to package my dll to XXXX. I am researching on it...

Thanks,
Susan