If you just want your external to link against another dll, that happens automatically with the MinGW build system. There are lots of externals that do this that are included in Pd-extended (as well as the DLLs).
.hc
On Mar 12, 2008, at 4:05 PM, best boy wrote:
ok, thank you very much for your help LoadLibrary() and GetProcAddress do the job now. and it seems to work :) bye bb
From: martin.peach@sympatico.ca To: ladataxi@hotmail.de; pd-dev@iem.at Subject: RE: [PD-dev] calling external code(.dll) from pd-external
(win32xp)
Date: Wed, 12 Mar 2008 19:00:21 +0000
best boy
maybe this is a misunderstanding. i try to explain. i want to write a pd external (which will be a dll on win). this pd external should contain code to call functions from
another dll
which is not pd-related
I think you would still use the same two functions: LoadLibrary
to load the
dll and GetProcAddress to find the address of the function you
want to call.
It won't make any difference if you call the dll from another dll
or an exe.
LoadLibrary() and GetProcAddress() are part of the Windows API
and not
related to pd.
Martin
This little bit from s_loader.c shows how pd loads externals,
which are
dlls
on Windows:
#ifdef MSW { HINSTANCE ntdll = LoadLibrary(filename); if (!ntdll) { post("%s: couldn't load external scheduler lib ", filename); return (0); } externalmainfunc = (t_externalschedlibmain)GetProcAddress(ntdll, "main"); }
Martin
Kostenlos bloggen + eigene Homepage + Fotospeicher = MSN Spaces Kostenlos! _______________________________________________ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------ ----
"It is convenient to imagine a power beyond us because that means we don't have to examine our own lives.", from "The Idols of Environmentalism", by Curtis White