POCO .h and .cpp file paths are included in stripped release executable, is it possible to prevent this?
I am building a fairly simple C++ program that depends upon the POCO library, statically linked, and my release build contains file path strings to all of the POCO headers and .cpp files that are used in the compilation. The executable is stripped, there are no debug symbols.