Re: dll not loading [message #42576] |
Tue, 15 February 2005 10:47  |
R.G.Stockwell
Messages: 163 Registered: October 2004
|
Senior Member |
|
|
"David Fanning" <davidf@dfanning.com> wrote in message
news:MPG.1c7beb6e8100b08989919@news.frii.com...
> I'm no expert in this area, but typically for DLMs or DLLs to
> be found automatically, they have to be in the IDL bin directory.
> If they are not, they can be pointed to with the !DLM_PATH system
> variable.
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming: http://www.dfanning.com/
ah, thanks David!
That solves the problem nicely.
Kinda weird how loading the file when IDL opens gets
around that though.
Cheers,
bob
|
|
|
Re: dll not loading [message #42577 is a reply to message #42576] |
Tue, 15 February 2005 10:20   |
David Fanning
Messages: 11724 Registered: August 2001
|
Senior Member |
|
|
R.G.Stockwell writes:
> A colleague reported an odd error with IDL code that calls
> Oleg Kornilov and Ronn Kling's avi dll, and I was able to reproduce it
> (win xp sp2, idl 6.1)
> I am probably missing something obvious, but what else is new :)
I'm no expert in this area, but typically for DLMs or DLLs to
be found automatically, they have to be in the IDL bin directory.
If they are not, they can be pointed to with the !DLM_PATH system
variable.
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
Re: dll not loading [message #42633 is a reply to message #42576] |
Wed, 16 February 2005 21:50  |
netnews.comcast.net
Messages: 10 Registered: October 2004
|
Junior Member |
|
|
R.G.Stockwell wrote:
> "David Fanning" wrote...
>
>> I'm no expert in this area, but typically for DLMs or DLLs to
>> be found automatically, they have to be in the IDL bin directory.
>> If they are not, they can be pointed to with the !DLM_PATH system
>> variable.
>>
> ah, thanks David!
> That solves the problem nicely.
>
> Kinda weird how loading the file when IDL opens gets
> around that though.
You have IDLDE set to "change directory on open" and IDL searches the
local directory, then the DLM_PATH for your .dlm.
So if you open your file up in IDLDE, the local directory is changed to
the directory containing your .dlm and IDL finds it. If you compile
your file from the command line your local directory is unchanged and
IDL can't find your .dlm.
-Rick
|
|
|