Unfortunately that is the way C++ works. Every include path must be explicitly listed. This is the nature of the beast. What most people do is include the base path and then use relative paths in the source files from there. For example assume the following:
\somelib
\audio
\graphics
\network
Add the somelib
path as an include path to the compiler.
#include "audio\audio.h"
#include "graphics\graphics.h"
#include "network\network.h"
Given that you're on VS 2013 still that is about the extent of your options. However if you upgrade to newer VS versions then you can start taking advantage of newer C++ features that will help move you away from this mess. One of the features I like is using vcpkg which handles at least the include/linking stuff for you in many cases. In the latest version of VS/C++ then you can start looking into modules which is a step away from includes. But all this requires more significant change to your code and won't help with any of your custom stuff.
Another option is to create a wrapper header file that includes the relative path files you care about (as shown above). Then reference that include file first in your source files instead. This would consolidate the pathing but requires you to update your files.