Andrew Lentvorski wrote:
> Today I got an error trying to compile Amarok. No big deal, right.
> Just fix the libraries and move on.
You listed C in the subject, and never once talked about it. What is
wrong with C?
I agree with Autoconf/Autotools. Very baroque. I don't care much for it.
C++ I do not care for, because it seems to break all the time.
C itself is mostly fine. The prepocessor may be a a bit whacked, but it
is relatively mindless.
I don't use KDE nor GNOME because of the whole huge chain of odd
dependencies, both when building and running. Start up a single GNOME
program, watch what else gets started for seemingly no apparent reason.
It boggles the mind.
Make, again, I have little problem with. Autotools and Autoconf use
recursive make, which can be quite harmful, and can break builds done
out of order.
Such as, you are trying to hunt down an error i na suport library in
a subdirectory, so you cd into it and invoke make. It can't, because
there is another dependency that it can't resolve because of the
recursiveness. If it builds, you still may not have something
workable as some other part may have affected the build in odd ways.
Basically, if I see something using recursive make I will, after
fixing a problem, make a clean build tree, apply the fix, and then
run make from the top. I do not trust clean or distclean targets.
Thank goodness for lndir.
I have heard of cons and scons, but never looked into them. I have no
idea how they work. Do you know of any projects that use them, as an
example of how they work?
I look forward to your next weekly column :)
-john
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
