Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#2037 change libwinspool.def to use spoolss.dll instead of winspool.dll

WSL
closed
Earnie Boyd
4.0.1 (1)
Bug
fixed
Feature_in_WSL_4.0
False
2013-09-15
2013-09-08
HighCommander4
No

Related

Issues: #2041

Discussion

  • Earnie Boyd
    Earnie Boyd
    2013-09-13

    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

     
  • Earnie Boyd
    Earnie Boyd
    2013-09-15

    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.

     
  • Earnie Boyd
    Earnie Boyd
    2013-09-15

    • labels: --> 4.0.1
    • status: unread --> closed
    • assigned_to: Earnie Boyd
    • Resolution: none --> fixed
    • Category: Unknown --> Feature_in_WSL_4.0