If someone were to use libPhil, right now they'd need to put their executable somewhere under the src directory (probably src/samples, like I've been doing)
But if someone wanted to use libPhil as a library / build system, they probably wouldn't want to put their stuff inside of it, but rather build their stuff parallel to it and just reference it.
If they use it as pre-compiled libraries, that's not such a big deal, but if they want to use libPhil's build system, then the build system needs to be set up to handle that (where would their compiled stuff go within the _winvs / _wingcc directories since it assumes everything is under the src directory)
Ideally they should set LIBPHIL_BASEDIR to where they have libPhil, and then set LIBPHIL_CWD to their own unrelated directory (at which point the build system will recurse into the libPhil libraries as it discovers headers included by them, etc)
If someone were to use libPhil, right now they'd need to put their executable somewhere under the src directory (probably src/samples, like I've been doing)
But if someone wanted to use libPhil as a library / build system, they probably wouldn't want to put their stuff inside of it, but rather build their stuff parallel to it and just reference it.
If they use it as pre-compiled libraries, that's not such a big deal, but if they want to use libPhil's build system, then the build system needs to be set up to handle that (where would their compiled stuff go within the _winvs / _wingcc directories since it assumes everything is under the src directory)
Ideally they should set LIBPHIL_BASEDIR to where they have libPhil, and then set LIBPHIL_CWD to their own unrelated directory (at which point the build system will recurse into the libPhil libraries as it discovers headers included by them, etc)