Hi Jon
I upgraded my autoconf, which solved my first problem. Now, everything runs fine until I get to the make install step, when I get this error:
make[2]: Leaving directory `/home/stevenlu/wine/dlls/x11drv' mydll.dll.so \ rm -f /usr/local/lib/libntdll.dll.so make[1]: mydll.dll.so: Command not found make[1]: *** [install] Error 127 make[1]: Leaving directory `/home/stevenlu/wine/dlls' make: *** [dlls/__install__] Error 2
Winedump created dlls/mydll/mydll.so, not mydll.dll.so.
Thanks for making those changes to the README, hopefully they'll get committed soon so other can avoid the problems I had.
-Steve
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
Hi Steve,
I upgraded my autoconf, which solved my first problem. Now, everything runs fine until I get to the make install step, when I get this error:
<snip>
The attached patch to winedump corrects the over-enthusiatic insertion of generated DLL entries into dlls/Makefile.in, and renames the MODULE from <dll> to <dll>.dll as per the current build process.
You can manually remove the offending lines youself, edit dlls/Makefile.in and remove the 2 lines referring to your DLL after the targets "uninstall::" and "install::". Then append".dll" to the MODULE = line in dlls/<yourdll>/Makefile.in. Alternately, apply the patch and regenerate.
I've just tested the process from start to finish and it works for me now. Let me know if you find any other issues. I've sent the patch to wine-patches/Alexandre.
Thanks for making those changes to the README, hopefully they'll get committed soon so other can avoid the problems I had.
np :-)
Jon