I've found various answers to this. The correct answer appears to be in tmp/work-shared/<machine>/kernel-source, but I didn't even have this directory, after doing a working build of core-image-minimal. After more searching, I discovered that this was because most of my build was from shared state. So I ran "bitbake linux-yocto-rt -c menuconfig", and it unpacked the kernel source into this location, but there was no .config file. I told menuconfig to save the current configuration under that name, but it said it hadn't changed, so didn't save it.
I ran menuconfig again, and told it to save it as "fooconfig", because I just wanted to look at it. This time, it didn't complain, but it didn't create that file either. So I ran it again, and told it to save it as "/home/pauld/fooconfig". That finally worked. So the minor question is: When I told it to save it as "fooconfig", why didn't it create that file in the kernel-source directory? Or did something in the do_menuconfig code subvert the menuconfig program and delete its output? The bigger question is: Where is the config file that is actually used to build the kernel? I'm trying various builds in different trees, and would like to compare the configurations. There must be _some_ file it's reading, mustn't there? -- Ciao, Paul D. DeRocco Paul mailto:[email protected]
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52594): https://lists.yoctoproject.org/g/yocto/message/52594 Mute This Topic: https://lists.yoctoproject.org/mt/81123624/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
