The README section on inserting the stub dll into the wine tree seems a little out-dated. It tells me to run autoconf, but autoconf complains that it cannot find configure.in - is this step still needed?
If I skip autoconf (which may be causing this problem), when I run make depend I get:
cd `dirname dlls/__depend__` && make depend make[1]: Entering directory `/home/stevenlu/wine/dlls' cd `dirname errh_auto/__depend__` && make depend make[2]: Entering directory `/home/stevenlu/wine/dlls/errh_auto' make[2]: *** No rule to make target `depend'. Stop. make[2]: Leaving directory `/home/stevenlu/wine/dlls/errh_auto' make[1]: *** [errh_auto/__depend__] Error 2 make[1]: Leaving directory `/home/stevenlu/wine/dlls' make: *** [dlls/__depend__] Error 2
I ran the install script that winedump produced, but maybe that's not up-to-date with respect to the current wine build process? Or am I just doing something else wrong?
-Steve
Jon Griffiths <jon_p_griffiths To: Steven Edwards steven_ed4153@yahoo.com @yahoo.com> cc: wine-devel@winehq.com Sent by: (bcc: Steve Lustbader/ANR/MS/PHILIPS) wine-devel-admin Subject: Re: WineLib and DLLs @winehq.com Classification:
09/12/2002 05:58 PM Please respond to jon_p_griffiths
Hi,
I'm writing a WineLib DLL that makes calls in my own Windows DLLs (not Wine's DLLs). I have the header files for those DLLs, and the Windows binaries for them. How do I link to them? Do I need to
wrap
them in spec files? What do I need to put into my Makefile.in?
look at tools/winedump. In spec mode it will generate everything you need to link to this dll - a makefile and dummy implementation, spec file and a script to insert it into your existing WINE tree (to link with). The README gives instructions for exactly this case (and some other more advanced ones).
Cheers, Jon
===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live
jon_p_griffiths@yahoo.com
__________________________________________________ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com
Hi Steve,
On Wed, 18 Sep 2002 18:57, steve.lustbader@philips.com wrote:
The README section on inserting the stub dll into the wine tree seems a little out-dated. It tells me to run autoconf, but autoconf complains that it cannot find configure.in - is this step still needed?
Yes, any time that you add or delete directories to the base distribution you need to re-run autoconf to generate a new configure script.
In your case you are running an older version of autoconf. Make sure that you are running autoconf version 2.53 or higher, or this process will not work.
There was a thread a while ago on allowing earlier versions of autoconf to be used to build Wine, but its not seen as too onerous to require a recent version for developers.
If I skip autoconf (which may be causing this problem), when I run make depend I get:
<snip>
Yes, you have the dll directory and a Makefile.in in there, but no Makefile, since configure didn't get updated and generate one for you.
I ran the install script that winedump produced, but maybe that's not up-to-date with respect to the current wine build process?
I updated the build process following the big changes earlier this year for building on Win32. I don't believe there are any problems, but there have been some changes since then. If you have any issues let me know and I'll try and iron them out. If I get a moment I'll update the README on requiring a new autoconf also.
I was considering allowing generated DLL'd to be built out of the tree but I didn't want to be generating too many files from winebuild (and autoconf files for a whole new dll project can be quite large).
Cheers, Jon