It is probably possible, but I'm not going to try it. You're of course free to try, but I recommend against it.
The possible gains are small and the possible problems are plenty, and as it is now, it works.
The fact that 4 files are recompiled is just sloppy programming. It is only really necessary to recompile one file (
configmanager-revision.cpp). If the application, the splash screen, and the about dialog used the static wrapper functions, they wouldn't have to be rebuilt at all.
However, the combined compile time for those 3 files is well under a second, while relinking the SDK takes some 10-15 seconds, so it's quite irrelevant. Don't optimise where there is no benefit to be expected.
Relinking the SDK is what is really painful, but it has to be done either way (as the object file could only be linked with the SDK). This means that the application will be relinked too, either way.
From an organisational point of view, where to put the
.cpp file? There would have to be an extra commandline option to specify a separate path, or it would go into
include.
How to compile the
.cpp file? It can't be added to the project. As the file is not under revision control, it does not originally exist. The IDE would notice that while loading the project.
Insert a dummy file? Modify the project while it is building using a script? Any other ideas?

All this to gain half a second of compile time?