Sorry about the question to do with visuall gcc. Alot of people seemed to
get a intolerable response to my question. The reason I posted it here was
a) I am lazy, b) On all the sites to do with Kdevelop the download links are
down, and c) I wanted to use the program to compile such files as schedule.c
and other scheduling algorithms I create. What do most of you use to comile
the kernel, just good ole' command line gcc.
Joe Harrington wrote:
>
> Sorry about the question to do with visuall gcc. Alot of people seemed to
> get a intolerable response to my question. The reason I posted it here was
> a) I am lazy, b) On all the sites to do with Kdevelop the download links are
> down, and c) I wanted to use the program to compile such files as schedule.c
> and other scheduling algorithms I create. What do most of you use to comile
> the kernel, just good ole' command line gcc.
Definitely. As much as I appreciate the efforts to make a workable
end-user GUI for Linux, I think people are still going to have to get
used to using command-line tools at the moment. For what it's worth,
there are two visual configuration options for the kernel; for a text
console, you can use "make menuconfig" while you can use "make xconfig"
if you're really into X. Personally, I found the standard "make config"
useful only the first time around, because it forced me to look at every
option, but it's much easier to undo mistakes using menuconfig or xconfig.