Bob Copeland wrote:
>
> On Wed, Jun 14, 2000 at 01:16:23PM +0530, Vivek Dasgupta wrote:
> > Have u called MAIN_WinelibInit first. How r u loading shared library?
> > Please give more details.
>
> All,
>
> Thank you for the answers. I haven't met with success yet, but I
> have a few more things to try when I get the chance to work on this
> project again.
>
> Just to give some more detail so people know where I'm coming from:
> I'm building a shared library to load a win32 DLL. The shared library
> itself also must be dynamically loaded from a program that is _not_
> linked against Wine. This is for a program that uses a plugin
> archtecture; I basically want to wrap a third-party DLL in the plugin.
>
> I'm using dlopen() in the program to load the .so, and the shared
> library then calls LoadLibrary() to load the DLL.
>
> I did not call MAIN_WinelibInit, as it is mysteriously missing from
> all wine code since the March snapshot. I'm not sure this is the
> "right" way to do this anyway. Moving back to an earlier snapshot
> and using MAIN_WinelibInit got me past the NtCurrentTeb() segfault,
> but crashed somewhere else in winelib. Anyone know what happened to
> MAIN_WinelibInit?
It has been removed since now the emulator and any winelib program
share most of the startup code. most current way of building a winelib
program is to use a .spec file (to create the module for the program
itself) - look into programs dir for some examples
doing the same type of thing by hand should also work
HTH
A+
--
---------------
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle