[NOTE: this concerns Visual Studio 2010 exporter - not sure how much of this is relevant to other exporters!]
The different build configurations within an export target only allow you to specify library search folders. It is only possible to specify the names of the linked libraries in the common exporter settings.
This is a problem, since an SDK I’m linking against places the debug/release libs in the same folder as each other, with a different filename (i.e., with a ‘d’ suffix for the debug version); thus the folders are common but the filenames are configuration-specific.
I’d rather not have to move them around each time there’s an update any chance of adding a configuration-specific version of the “External libraries to link” property? I guess it could get merged with the common list when exporting.