Xen Cloete wrote:
No, it isn't. Below is your setting copied from your other posting. I snipped the irrelevant stuff. libxml2.lib isn't there.Yip that's correct. VC++ 6.00.I assume you mean Visual C++ 6.0, not one of the newer .NET ones.Forgive me for asking the obvious: did you add libxml2.lib to the "Object/library modules" field of the Link tab of the Project Settings dialog?Yip it certainly has been added. See my setting with the reply to GORKA.
Link Tab: Object/library modules:Ws2_32.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib
My understanding of the .lib files is that these files are not the same as .dll files. To read .dll files you would obviously use the LoadLibrary and GetProc... functions to load into memory and then accessthese functions.
That's not true. When something is compiled a a DLL, it also produces a lib file. That lib file can be included in your linker setting, and there is no need to do LoadLibrary and GetProc jazz. Just call the functions as you normally would. Make sure the .DLL file is somewhere the .exe can find it though. You CAN use LoadLibrary, etc. You just don't HAVE to.
Static lib files are different from .DLL files. You just link with the .lib file at compile time. You don't need LoadLibrary, etc. in this case either. Just call the functions.
This is certainly not the normal way of linking with a library at compile time.The "resource file section" sounds like the wrong place to add a library. Similarly, the location of libxml2's headers should be in the "Additional include directories" field of the Preprocessor section of the C/C++ tab, not the "Additional resource include directories" field of the Resources tab.You are probably correct. However let me throw a spanner in the works. I have the production application setup this way. This was done by previous C/C++ developer. And this works. I have setup everything the same as the production applications settings. But no luck!!