Re: Calling type library dll NOT from project directory
- From: Alex <alsim123@xxxxxxxxxxx>
- Date: Mon, 16 Jul 2007 11:57:04 -0700
On Jul 16, 12:10 pm, "David Ching" <d...@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
"Alex" <alsim...@xxxxxxxxxxx> wrote in message
news:1184592903.910948.289470@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi, everybody
I have to implement some SDK in my MFC project. I've added
corresponding library to the project and copied corresponding dll
file to my project directory. But this doesn't work because this SDK
was created the way that this dll cannot be copied anywhere, but it
must be called from the directory where SDK setup put it. Import
directive doesn't work I'm getting an error:
"Cannot open type library file:..."
So is it possible to indicate (spedify) somehow in my project the path
to this dll, unless it's residing not in project directory?
Thank to everybody in advance who bother to answer.
Alex
Alex, most SDK's install to a certain folder so that they can keep headers,
libs, dll's, doc, etc. all together. But that doesn't mean that the dll
must stay where it put it. In fact, how are you supposed to deploy your app
(that you need to ship the dll with) if you *don't* copy the dll and put it
in a convenient place for your .exe? You aren't supposed to run the SDK
install package every time you deploy your app are you? I would just copy
the dll from whereever the sdk put it into your app's folder.
-- David- Hide quoted text -
- Show quoted text -
David, you are exactly right and reasonable - if you have to implement
some SDK, you can expect exactly what you mentioned above. But in
real life sometime you have to deal with bad designs and decision (or
I'm suspecting this SDK is really old). So, as I mentioned in my post
#4, the only way I can implement this SDK is explicit linking. This
means a lot of extra typing, but nothing I can do about it. At least
this way these SDK functions work properly. And answering your
question about the deployment of my application you were right - my
exe can be run only on the machine where the "main product" which this
SDK was created for, has been installed. So somewhere there will be
this dll (the path to it I will be able to read from the registry).
It cannot be run on a "clean" machine.
Alex
.
- Follow-Ups:
- Re: Calling type library dll NOT from project directory
- From: xrxst32
- Re: Calling type library dll NOT from project directory
- From: David Ching
- Re: Calling type library dll NOT from project directory
- References:
- Calling type library dll NOT from project directory
- From: Alex
- Re: Calling type library dll NOT from project directory
- From: David Ching
- Calling type library dll NOT from project directory
- Prev by Date: Re: How to Declare Pointer to Member Function?
- Next by Date: Re: Calling type library dll NOT from project directory
- Previous by thread: Re: Calling type library dll NOT from project directory
- Next by thread: Re: Calling type library dll NOT from project directory
- Index(es):
Relevant Pages
|
