Does ppremake do any dependency checking?
I was having a terrible time building panda with ppremake. I read the docs
and at first the only thing I put in my Config.pp was to have it point at my python includes.
Started getting errors while building dtools about prtypes.h. Google
searched and that seemed to be Mac related ( I am running
Slackware Linux 10.1). Added…
#define BUILT_TYPE unix
… to Config.pp and it fixed that problem. I was then able to build dtools.
Anybody here of this before? Am I incorrect in the understanding that
you only put what is specific about your system in the top level Config.pp?
Anyway went to build panda without NSPR (see previous post) and started
getting CG compile errors about pthreads. “#defined HAVE_CG” to nothing
and got CGGL errors about pthreads! “#defined HAVE_CGGL to nothing” and
I still got errors about pthreads!.
I was doing make cleans, going back to dtools, running make clean, ppremake, make, make install before returning to panda and doing
ppremake, each time I edited Config.pp.
Still make was giving me these errors.
Looking back, I probably should have added “#define HAVE_NSPR” to my
Config.pp but I think I was expecting some kind of dependency check.
I mean if you need NSPR for threads, and you don’t have NSPR, and if CG and
CGGL need threads, then why was ppremake trying to build them? Does ppremake do dependency checking like make?
Anyway I couldn’t figure out how to install NSPR “system-wide” so I just put
it next to panda3d and edited Config.pp to point to it like David suggested.
Got all the way through the build system. Everything working fine!
So do you all think I have found a bug? I wonder if anyone else has had similar
B.T.W. What do you all call it when you undefine something by “#define”- ing
it to null? ppremake syntax makes my brain hurt. Talking about it makes
it hurt worse!