As emailed to me by "guy-kde", the errors messages encountered when running kdesrc-build without the essential build development programs installed are kind of confusion. kdesrc-build already checks for "make", so it should also check for programs like gcc, cmake, pkg-config, etc. The gcc check should probably be left to cmake (as there are other compilers which can be used, llvm, icc, etc.), but overall I don't think it's a bad idea to pre-stage some checking and fail early if possible.
Git commit 67ad3fa3dab3818a78076feb4513d0ab71aca693 by Michael Pyne. Committed on 30/03/2012 at 06:12. Pushed by mpyne into branch 'master'. Add check for "essential" programs before building. If you (for whatever reason) don't have things like cmake installed before trying to run a full build you'll just spend a lot of time to eventually figure out that kdesrc-build wasn't able to build anything. Now we can (optionally!) skip the build process entirely if "essential" programs do not seem to be available before running the build. Each build system type is able to determine which programs are considered essential. Note that if 'qmake' is the only holdup then we don't complain if we seem to be building Qt or if we're in pretend mode (since it's certainly possible to fool build system detection when in pretend mode). If qmake is really missing the user /should/ just find out when they run without --pretend (since then Qt should show up amongst the build-modules' build systems). FIXED-IN:1.15 M +99 -0 kdesrc-build http://commits.kde.org/kdesrc-build/67ad3fa3dab3818a78076feb4513d0ab71aca693