nvda

e62ac062 - Make sure that the input library for nvdaControllerClient (nvdaControllerClient32.lib or nvdaControllerClient64.lib) properly points to the correctly named dll (e.g. nvdaControllerClient32.dll for nvdaControllerClient32.lib). Previously both 32 and 64 bit libs were pointing to nvdaControllerClient.dll, which did not exist.

Make sure that the input library for nvdaControllerClient (nvdaControllerClient32.lib or nvdaControllerClient64.lib) properly points to the correctly named dll (e.g. nvdaControllerClient32.dll for nvdaControllerClient32.lib). Previously both 32 and 64 bit libs were pointing to nvdaControllerClient.dll, which did not exist. Specific changes: *Remove the LIBRARY statement from nvdaControllerClient.def. Link seems to cope fine with out it, producing no warnings, yet still properly exports all listed functions and uses the real name of the dll. *Remove special code in client/sconscript that handled dependency tracking of the .def file and the addition of the /def: switch to LINKFLAGS. It seems that the SharedLibrary builder from the msvc SCons tool is much smarter than I thought; providing a .def file as one of the source files automatically uses the .def file properly (i.e. adds it with a /def: switch).