On Fri, 28 Apr 2000 11:06:17 +0100, Ian Dash <[EMAIL PROTECTED]> wrote:
> My problem lies with the search path used to find the DLL - after
> playing around with making the ppd and installing it I've found out
> that it only looks in the current executing directory, within the
> path statement, and in the system directories (system32 under NT,
> system under 95), this is backed up by the DevStudio Docs which say
> this about DLL search paths:
Yes, that's the way WIn32 works.
[...]
> Ideally I'd like to be able to put mydll.dll into the same
> directory as the module's DLL and for the module to load it from
> there.(i.e that it finds it in C:\Perl\site\lib\auto\mypackage\modname\)
>
> Is there a way of doing this? Is it something todo with Implicit
> V's Explicit linking? Can I solve this by specifying something in
> MakeFile.PL - I've had a poke around in the docs for Dynaloader and
> see that @dl_library_path might help me out...but I'm unsure where
> or how to sort this out!
You could do some "explicit" linking stuff, like calling LoadLibrary()
with a full path and getting pointers to the functions with
GetProcAddress(). This will allow the additional flexibility at the price
of more programming work.
-Jan
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
