Re: Problems converting DLL to unix SO with winelib

[List vmn]

Hi Martin,

I finaly got the patch to work.
The problem was with my mail client.
I am now at the office and using eudora and things worked...

A question,
When I use the patched winemaker , I get a spec file with out any imports 
at all, even the ones
specified on the command line.

When I compile/link  I get unresolved symbols.

I then dont know what to do so I add the import lines back to the spec file 
and it links/compiles....

What am I missing here?

What is your patch doing ?

Thanks,
Miguel

At 17:17 7/6/2002 +0200, you wrote:
> Am Fre, 2002-06-07 um 16.59 schrieb [e-mail]:
> > Here is the output...
>
> And here is mine:
>
> [martin@biker tools]$ cvs diff -u -r 1.39 winemaker
> [martin@biker tools]$ cd ..
> [martin@biker wine]$ patch -p0 --dry-run </tmp/winemaker.diff
> patching file tools/winemaker
> patching file documentation/winemaker.man
> [martin@biker wine]$
>
> Perhaps you have the wrong patch. I attach it.
> Martin
>
> --
> Martin Wilck                Phone: [phone]
> Fujitsu Siemens Computers   Fax:   [phone]
> Heinz-Nixdorf-Ring 1        mailto:[e-mail]
> D-33106 Paderborn           http://www.fujitsu-siemens.com/primergy

Problems converting DLL to unix SO with winelib

[Martin Wilck]

Am Die, 2002-06-11 um 18.27 schrieb List vmn:
> What is your patch doing ?

First of all, the patch may be far from perfect, I made it to suit my
own needs. I am happy about bug reports.

It is correct that there are no more imports in the spec file.
The import libraries are put in the Makefile.in instead, in the
xyz_IMPORTS variable, where xyz is your project name (have you rerun
./configure ?).

Martin

Problems converting DLL to unix SO with winelib

Thanks,
Late last night I was looking at the makefile and saw that I could 
put the imports there. I tested this and it worked.
I will put it in the makefile.in next...and then rerun configure.

winebuild is receiving the import parameters like gcc does for includes and 
linking...

Thanks for helping me get this far.

My main question now is:
Winemaker creates my winelib *.SO as libmytest.so .
When trying to use is in my test app...

I can´t get winebuild to understand the libmytest.so name.
I have to copy libmytest.so to libmytest.dll.so
I then tell winebuild to import libmytest.dll or libmytest
I ALSO have to tell gcc to link mytest.
If I dont tell gcc to link mytest I get unresolved symbols in the final
linkage of the winelib app.
If I dont tell winebuild to import libmytest.dll then the winelib DLL
is not correctly initialized at run time.

It seems strange to me to have to link with GCC and import with WINEBUILD.

Is this correct?

If so, then ideally winemaker -dll should generate names like mytest.dll
instead of libmytest.so? Or winemaker after make install should create symlinks
like
/usr/local/lib/libmytest.so -> mytest.dll.so

Miguel

----------------
> First of all, the patch may be far from perfect, I made it to suit my
> own needs. I am happy about bug reports.

Sure, I am using it!
> It is correct that there are no more imports in the spec file.
> The import libraries are put in the Makefile.in instead, in the
> xyz_IMPORTS variable, where xyz is your project name (have you rerun
> ./configure ?).

Yes.

-------------------------------------------------
This mail sent through IMP: webmail.vmn.com.br