> anjunta - i just tried this recently and it has a wizard that walks I believe that's anjuta, not anjunta.
Yet another tool to manage a tool (autoconf) that makes use of another tool (automake) that's implemented using a couple of other tools (m4 and perl) that controls a tool (make) to manage a language. And all you wanted to do was write a helloworld program! =). With all these layers, only the elite end up understanding what really goes on behind the smoke and mirrors. Once you invest the blood and sweat needed to set up your autoconf scripts, your program (in theory) is going to compile with the probably hundred or so systems which the autotools have been ported to without your ever having to worry about tailoring your C/C++ code for their idiosyncracies. All the user has to do is type ./configure and he's all set. Amazing, eh? Of course, it's really because of C/C++'s shortcomings that tools like autoconf->automake->make are needed (not to mention the evil and much-abused preprocessor). To get an idea of how klunky the whole process is, imagine: you're using *at least* 3 different text processors: m4, perl and the C/C++ preprocessor!! Make is hardly needed for most Java projects. While with Python, it's not even something you need to think about. Of course, neither is anywhere near as fast as C. > kdevelop - so far this is the hands down champion of OSS IDE's. it has > a wizard for starting any type of app from KDE, QT, GNOME and console Graphical IDEs... pwe! Have never really been that endeared to them from the time I first used them with Borland C++ 3.1. A good text editor plus a good OS shell and the requisite command-line tools should be all the 'IDE' you need. They're more universal and the expertise you spent so much time gaining can be reused for whatever different compilers/languages you find yourself using. It may be that I haven't tried doing any *REALLY BIG* projects which is why I don't find myself needing them. Still, I can't stand not knowing what the IDE does behind my back (read: MSVC pre-compiled headers). I guess IDEs _may_ be a benefit, but for them not to trip you up, you have to invest even more time learning their ins and outs. In other words, I find that they ADD to the learning curve, not reduce it. It's actually a better idea to start with command-line tools first before moving up to using them (if you really do find them of help that is). _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
