ok - I think I know what this is now…
I never saw it, because I always had checked:
tools -> compilers -> use fast but imperfect makefile generation
when you turn that off, you get the ‘pp’ target problem.
after playing with it for several hours yesterday, I learned that the length of the relative path presents a problem. for example, this:
gives issues when the fast but imperfect generation is turned off. it messes up the makefile generation somehow. I don’t know why, but is makes the makefile like this:
obj/ofCvGrayscaleI.o: ../../libs/openFrameworks/cvthisisalongasfoldernameyo/ofCvGrayscaleImage.cpp pp
thus the ‘pp’ issue…
when you use a short path:
this will compile fine…
(actually cv/ofCvGrayscaleImage.cpp is about on character too long, but it compiles fine when I shorten that)
obviously this is a huge pain, especially with addons. I’m going to test it a bit more so I know what the limits are…
it appears that this problem is based on path length + “use fast but imperfect makefile generation” being turned off.
ps : seeing this renewed our interest in discovering some pc alternatives, like code::blocks or eclipse… for now, we will continue to support devcpp, but this is a pretty nasty problem for us, since our addon paths can be quite long…