Alexandre, The winspool.drv issue is a lot more serious than the in-tree execution. This one screws things up badly for the PuTTY build system. Should we modify winebuild to try to link with winspool.drv, and if that fails with winspool.dll when -lwinspool is given? (or the other way around, I don't know) I'd really appreciate help on this one, so I can send the patch out. -- Dimi.
"Dimitrie O. Paun" <dpaun(a)rogers.com> writes:
The winspool.drv issue is a lot more serious than the in-tree execution. This one screws things up badly for the PuTTY build system. Should we modify winebuild to try to link with winspool.drv, and if that fails with winspool.dll when -lwinspool is given? (or the other way around, I don't know)
The right approach would be to implement import libraries. This is already on my TODO list, I'll bump the priority a bit... -- Alexandre Julliard julliard(a)winehq.com
The winspool.drv issue is a lot more serious than the in-tree execution. This one screws things up badly for the PuTTY build system. Should we modify winebuild to try to link with winspool.drv, and if that fails with winspool.dll when -lwinspool is given? (or the other way around, I don't know)
The right approach would be to implement import libraries. This is already on my TODO list, I'll bump the priority a bit...
Thanks Alexandre. I tried to do this a while back but was having problems understanding something in the makefiles for my "make implib" rule. A fix for the import libs would be great because I have this same problem when building certain dlls under mingw and keeping the mingw win32api package and wine in sync is a big waste of time for me. C:\mingw\bin\..\lib\gcc-lib\mingw32\3.2\..\..\..\..\mingw32\bin\ld.exe: cannot f ind -lwinspool.drv C:\mingw\bin\dllwrap.exe: C:\mingw\bin\gcc exited with status 1 make: *** [comdlg32.dll] Error 1
"Dimitrie O. Paun" a écrit :
Alexandre,
The winspool.drv issue is a lot more serious than the in-tree execution. This one screws things up badly for the PuTTY build system. Should we modify winebuild to try to link with winspool.drv, and if that fails with winspool.dll when -lwinspool is given? (or the other way around, I don't know)
be aware anyway that in some cases we have both foo.dll and foo.drv (checkout msacm...) so import libs are the way A+
On November 22, 2002 01:12 pm, Eric Pouech wrote:
be aware anyway that in some cases we have both foo.dll and foo.drv (checkout msacm...) so import libs are the way
That's what Alexandre was saying too :) I've fund a way to work around it for PuTTY, but we need to fix this as -lwinspool is very common, and most build systems are hard to hack to change them to winspool.drv, if you want to share your build system between Wine, and Windows... -- Dimi.
participants (4)
-
Alexandre Julliard -
Dimitrie O. Paun -
Eric Pouech -
Steven Edwards