none
linked dll for release version RRS feed

  • Question

  • HI,

    I have a Debug/Relese version for my project, for the Debug I have included the checkres70d.lib , and for the the release I have included the checkres70.lib, but My release .exe dos not run , it asks for the checkres70d.dll, I dont know why !! I have not included the path for  checkres70d.lib for the release version in the link->general, and not the checkres70d.libin link->input !!!! i have added the checkres70.lib !!!!

    anny help please !!?

    best regards

    Monday, May 30, 2011 1:56 PM

Answers

  • But the think that I still don't get it :

    that (if to set the dependency DLL we enter the corresponding .lib in link->input) so why I it stil depends on d.dll while I enter the I am expecting the .dd cause in adde the .lib file in the link->input configuration ???

     

    • Marked as answer by BobMSDN Monday, May 30, 2011 8:16 PM
    Monday, May 30, 2011 8:09 PM

All replies

  • you can use dependency walker for find which DLL or exe depends on checkres70d.dll? The application may not depend on  checkres70d.dll. But, some application(exe) dependency DLL might depend on checkres70d.dll.

    you can also check linker command line for executable.


    Thanks and Regards Selvam http://www15.brinkster.com/selvamselvam/
    Monday, May 30, 2011 3:30 PM
  • thank you for you respond,

    But My release.exe don't event depend on checkres70.dll, I only see the checkres70d.dll !!!!

    thanks again .

     

    Monday, May 30, 2011 6:35 PM
  • when I see put tha in dependency Walker, I see checkres70d.dll rather than checkres70.dll
    Monday, May 30, 2011 6:36 PM
  • BobMSDN wrote:

    I have a Debug/Relese version for my project, for the Debug I have  included the checkres70d.lib , and for the the release I have
    included the checkres70.lib, but My release .exe dos not run , it asks  for the checkres70d.dll, I dont know why !!

    How was checkres70.lib produced in the first place? By all appearences,  it refers to checkres70d.dll.


    Igor Tandetnik

    Monday, May 30, 2011 6:48 PM
  • I have no idea, but at least I will see in the dependency walker that my .exe depends on checkres70.dll and then I will see that the checkres70.dll depends on checkres70d.dll, but all a see in dwpendency walker is that my release .exe depends only on checkres70d.dll  !!!

     I don't understand

    please help

    Thanks :)

    Monday, May 30, 2011 7:09 PM
  • BobMSDN wrote:

    I have no idea, but at least I will see in the dependency walker that  my .exe depends on checkres70.dll

    No you won't. If you link to checkres70.lib (that's .lib, not .dll), and  it refers to checkres70d.dll, then your EXE ends up depending on  checkres70d.dll. checkres70.dll is nowhere in this picture, since no  .lib file refers to it.


    Igor Tandetnik

    Monday, May 30, 2011 7:39 PM
  • But the think that I still don't get it :

    that (if to set the dependency DLL we enter the corresponding .lib in link->input) so why I it stil depends on d.dll while I enter the I am expecting the .dd cause in adde the .lib file in the link->input configuration ???

     

    • Marked as answer by BobMSDN Monday, May 30, 2011 8:16 PM
    Monday, May 30, 2011 8:09 PM
  • sorry i am expectiong the .dll file

    :)p

    Monday, May 30, 2011 8:10 PM
  • BobMSDN wrote:

    But the think that I still don't get it :

    that (if to set the dependency DLL we enter the corresponding .lib in  link->input) so why I it stil depends on d.dll while I
    enter the I am expecting the .dd cause in adde the .lib file in the  link->input configuration ???

    The problem seems to be with the "corresponding" part. It looks  suspiciously like checkres70.lib actually corresponds to  checkres70d.dll, and not to checkres70.dll as the file name would  suggest.

    Realize that the lib file's name doesn't mean anything. If you have  abc.lib that refers to abc.dll, linking to it introduces a dependency on  abc.dll - so far so good. Now, you can rename the lib file to xyz.lib,  link to that - and you would still depend on abc.dll, not on xyz.dll.


    Igor Tandetnik

    Monday, May 30, 2011 8:42 PM
  • I will check that, thank you verry much buddy ;)
    Monday, May 30, 2011 8:45 PM
  • Hey Igor, thank you verry much buddy it realy works, My lib refers to the wrong dll, thanks again, may I have you contacte please ;)

    Hav a nice day

    Tuesday, May 31, 2011 2:09 PM