projectGenerator needs testing

considering LOTS of different situations it is supposed to handle:

addons (regular ones)
local addons (inside project folder, outside, relative or absolute)
addons which have other addons as dependencies, but not specified on addons.make (maybe some addon depends on ofxOpenCv for example)

props, libs, dylibs, frameworks

Project inside other project ( new feature to help addons like [ofxKinectForWindows2] )
(https://github.com/elliotwoods/ofxKinectForWindows2)

Dylibs are now bundled inside app which is great, maybe we can develop an application and run in other computer with all dylibs bundled, but there are some issues to fix. Let's say if we are going to use ofxHapPlayer we have to fix dylib paths in a script, so it works. (or maybe ask developers to do this modification there?)

all possible platforms
platforms generating templates to other platforms, which I notice it has issues, because it depends of the presence of the library files installed for other platform. I'll cc @danoli3 and @ofTheo in this one. Are we supposed to install libs for differnt platforms in the same OF installation?

Additional source folders
Again with relative to project, relative to other folders or absolute.

Start with the projectGenerator entry points that handle addons, libraries, project paths, source folders, dylibs, and platform templates. Reproduce the listed combinations, including nested projects and cross-platform generation, then document or test each supported case and the remaining dylib-path and library-availability issues.