On Fri, Sep 13, 2013 at 7:52 AM, Andy Rushton wrote:
I have followed this thread and tried out the various suggestions - changing
winspool.dev to point to either winspool.drv or spoolss.dll, then rebuilding
according to Earnie's instructions, but neither worked for me even though I
have both on my system - winspool.drv is in SysWOW64 and spoolss.dll in
System32. This is on a 64-bit Windows 7 machine, up to date and service packed.
Linking against wxWidgets without the -lwinspool does give linker errors, so
it is a wxWidgets dependency, not a mistake in the wxWidgets build system.
Downloading winspool.dll from dll-files.com (yes, I know, risky) and
dropping it into the same directory as the exe did work, so then I tried
copying SysWOW64/winspool.drv to winspool.dll alongside the exe and that
works too. So this is a workaround for now.
The one experiment I haven't tried is reinstalling wxWidgets after
reinstalling w32api - I'm assuming this is a link-time problem, but I
suppose it might be a dependency of the wx DLLs. Anyone know?
Andy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The real issue here is that process creating libwinspool.a used winspool.dll instead of winspool.drv. The Makefile.in was modified to use the correct DLL name when creating libwinspool.a.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On Fri, Sep 13, 2013 at 7:52 AM, Andy Rushton wrote:
The real issue here is that process creating libwinspool.a used winspool.dll instead of winspool.drv. The Makefile.in was modified to use the correct DLL name when creating libwinspool.a.