Why can windows find the dlls?
.lib and a file with extension .dll are created. The .lib is required during the compilation process as it tells the compiler the classes and functions that have been exported. The .dll is needed during execution. The compiler needs to know the directory path where to find these .lib and .dll files. Similarly, when running the executable, the system needs to know where to find the .dll files. MS Windows provides a mechanism for specifying search paths for .lib and .dll files. Edit the path environment variable to include the directory where the OOPSMP libraries are located. When compiling in debug mode, the executable is created in OOPSMP\projects\bin\debug\ and the libraries are created in OOPSMP\projects\lib\debug\. Similarly, when compiling in release mode, the executable is created in OOPSMP\projects\bin\release\ and the libraries are created in OOPSMP\projects\lib\release\. So just add the following three paths to the PATH variable: • path\OOPSMP\projects\lib\ • path\OOPSMP\projec
Related Questions
- I often call special functions (including Windows API functions) in DLLs from Visual Basic 3.0 and Visual Basic 4.0. Can I do this in VBA?
- Id like to probe routines in the Windows sockets DLLS. Any issues I should be aware of?
- How do I fix link errors about missing functions when compiling DLLs on Windows?
