Back when I had the time to compile my own kernels there was a terminal GUI that I used to configure it. Is that gone now?
-
-
Replying to @andrioid
sure, there's menuconfig. I wouldn't call that user-friendly...
1 reply 0 retweets 0 likes -
-
Replying to @hugelgupf @andrioid
and the dependencies are oh-so-often so wrong all you get is a compilation error then you have to dig into code to see what broke and what might supply that dependency which means you gotta know how the Kconfig build system actually works (
#define and the makefiles)1 reply 0 retweets 0 likes -
Replying to @hugelgupf
Sounds like the Linux kernel could benefit from lowering this barrier to get some new developers to the project Maybe the
@linuxfoundation should sponsor that effort?1 reply 0 retweets 1 like -
Replying to @andrioid @linuxfoundation
tbh i don't have any good ideas on how to make it better right now just a frustration i had starting out, and one i see in everyone we onboard to LinuxBoot internally
1 reply 0 retweets 1 like -
seriously make menuconfig is WAY better than anything else out there in the autotools/CMake/NIHbuildSytem world for complex projects
2 replies 0 retweets 0 likes -
Replying to @acruiz @hugelgupf and
I don't think that
@hugelgupf was complaining about the tooling (I agree that Kbuild is way better than most build systems) but rather the fact that it's common for option dependencies to not be properly defined in the Kconfig files. What's hard is to figure out the implicit deps1 reply 0 retweets 1 like -
Replying to @martinezjavier @hugelgupf and
To me that's a slightly different problem than the setup being hard for newcomers. Rather than the setup being buggy and those bugs being specially harming for newcomers. It's not like those bugs don't hit seasoned developers either.
2 replies 0 retweets 0 likes -
Replying to @acruiz @martinezjavier and
Well, less than they used to since we've got bots randomizing that these days. But that's not ever going to solve the problem of not having any real way to tell what's *important*.
1 reply 0 retweets 2 likes
Yeah, although again I'm not sure if that's a problem with the tooling. I suggested in a previous tweet that maybe we should have some sort of "feature catalog" that contains config fragments and use scripts/kconfig/merge_config.sh to choose what's needed and generate the .config
-
-
Replying to @martinezjavier @vathpela and
Most people already do something like that. So it would be good to have a curated list of config fragments that contains symbols to enable + dependencies for certain features instead of everyone duplicating the same in their build systems.
0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.