This looks great! Is the code for any of the extensions available somewhere? There are two quirks I'm seeing on the VS plugin:
- make sure to not select
Create directory for solutionwhen making a project, otherwise you'll get the notice about the OF path being wrong - When removing addons, the header include paths are sometimes not removed?
Regarding the ofxAddonLib pattern, I've been thinking about this a bit recently. There are a couple things you can do with this approach that addon_config.mk doesn't support, or that I can't figure out, as I've been trying to set up an addon_config.mk to use with ofxKinectForWindows2. For example, the addon links against a globally-installed kinect20.lib at $(KINECTSDK20_DIR)\Lib\[x86|x64]. Normally the pg will set up the libs based on the folder structure inside the addon, but adding ADDON_LIBS += $(KINECTSDK20_DIR)\Lib\x64\kinect20.lib to the file doesn't add anything to VS's linker settings. Maybe it can't resolve the environment variable path and thinks the lib doesn't exist? Either way there's no way to specify the architecture.
I know this has been discussed a bit here, and I agree that the additional vxproj/props files seem redundant...maybe addon_config.mk can become a little more robust so that the AddonLib isn't necessary?