IMHO it would be better if the raspicam library is installed as a shared/dynamic library in the normal RPi library directory the way the install of the library itself does. I don’t see any good reason why not. Your wiringPi example uses the install provided by the library itself and installs it as a shared library in the standard library path, very clear, why not with raspicam as well.

I have the cam working on the RPi now and compile stuff on the console. I’m now trying to get the cross compiling for raspicam to work using the same approach you have used in the wiringPi example, but the problem is that VisualGDB has no help system (?) which makes it very hard and time wasting to try to finding out on your own what to do.

BTW. I think you could probably get a lot of friends if you made the VisualGDB available for QtCreator both Windows and Linux. These days I don’t use my VS2013 almost at all but now for VisualGDB only.