Why do we need debug libraries and pdb files?
For the stripped-down version of Qt provided in the BCI2000 source tree, no source code is available, and debugging information in the Qt libraries cannot be used for debugging. Thus, it appears that always linking to the release version of the Qt libraries would be sufficient, saving considerable space in the SVN data base, and download time for the user. Unfortunately, it turns out that this is not sufficient, and that both debugging versions of the Qt libraries, and associated pdb files, are required in the BCI2000 source tree. • MSVC does not cleanly separate between compile and link stages. Rather, the compiler provides /M switches that determine the runtime libraries to be used in the linking stage. • Due to this dependency of object code on certain runtime libraries, it is not cleanly possible to link together static libraries compiled with one /M switch with application code compiled with another /M switch. Thus, we need to provide both release and debug versions of the Qt libr
Related Questions
- I would like to compile a project using some non-standard libraries. How can I indicate to CodeBlocks that these libraries and include files exist?
- My project uses COM objects, and requires DLLs and type libraries to compile some of my files. How does IncrediBuild handle this?
- Can ADEPT Suite work with AFP files with inline resources and resources called from libraries, interchangeably?
