If you need to single step through your code code then your code must be built with debug symbols. As you step through your code and it enters Qwt functions in the library you will either:
- See a low level disassembly of the release mode Qwt library routine, or
- A high level source code view of the debug mode Qwt library routine. (The source is embedded in the library to enable this.)
It seems unlikely that you want/need to debug the Qwt code. You can Step Over the Qwt calls to avoid the disassembly.
I am not intimately familiar with Windows Qwt builds. I assumed that the debug mode Qwt library would follow the same convention as the Qt libraries; appending a 'd' so that release and debug can exist side-by-side. If the debug library gets the same name, i.e. qwt.dll, then you are better off building release mode and installing into Path A, and debug mode installed into Path B and adjust INCLUDEPATH and LIBS accordingly.
I also assumed a directory structure. You will have to adjust paths to suit what has actually happened on your machine.
Bookmarks