It's not possible in general - static libraries and executables are completely different kinds of animal. The way to handle this situation is to create two projects - one for the library, which contains all the functionality. And one for the executable, which is a thin wrapper that simply calls functions in the library.
If any symbol in a Application (.exe) project is exported (e.g. With __declspec(dllexport) ), both the . Exe and the . Lib files will be generated See: Why does my Visual C++ .
Exe project build create . Lib and . Exp files?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.