Doesn't matter if you use it, if it's linked then something you're
using is using it.
If it isn't lazy linked, just one failed symbol import will fail the
whole DLL dependency tree. No idea what might cause that in your
case, maybe there's a mixing of different versions of system DLLs by
vario
Hi Niall,
Thanks a lot for your time.
I checked all the DLL's. Everything is showing ok. Only one is, IEFrame.DLL
and in that for one function it is showing red in color. Function name as
"#270".
We are not using that function/DLL anways.
Regards,
Raju.
On Thu, Jun 21, 2012 at 3:23 PM, Niall D
With DW it's not so much that the libraries are present, but to check
that there are no failed symbol imports. Your error suggests a failed
symbol import.
Niall
On 21 Jun 2012 at 14:34, Nagaraju wrote:
> Hi Niall,
>
> I have used the DW and all the libraries are present.
>
> The same code wo
Hi Niall,
I have used the DW and all the libraries are present.
The same code works, if I use LoadLibrary in C++. But when I try to build
the C++ DLL code with extention ".pyd", it is throwing error.
FYI, the C++ Class names are mangled.
Regards,
Raju.
On Thu, Jun 21, 2012 at 2:30 PM, Niall Do
You might find Microsoft's Dependency Walker useful.
http://www.dependencywalker.com/
Niall
On 21 Jun 2012 at 10:01, Nagaraju wrote:
> Hi All,
>
> I have written a C++ DLL. That DLL depends on some other libraries. I have
> kept all those dependent libraries in the release folder.
>
> Now in
