From: Randy Dunlap <rdunlap@infradead.org>
To: Ulf Magnusson <ulfalizer@gmail.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Kconfiglib menuconfig implementation
Date: Sat, 19 May 2018 20:45:04 -0700 [thread overview]
Message-ID: <c4ec710f-b2bd-b9f0-c33a-159aa53ca73c@infradead.org> (raw)
In-Reply-To: <CAFkk2KRWon_S--dxYw82cDyGXKTFA6jxrrQwstzLvHPs=6-dqQ@mail.gmail.com>
On 05/08/2018 09:59 AM, Ulf Magnusson wrote:
> Hello,
>
> I've added incremental search for jumping directly to a symbol now.
> Regular expressions are supported as well.
>
> Some screenshots below:
>
> https://raw.githubusercontent.com/ulfalizer/Kconfiglib/screenshots/screenshots/ss10.png
> https://raw.githubusercontent.com/ulfalizer/Kconfiglib/screenshots/screenshots/ss11.png
> https://raw.githubusercontent.com/ulfalizer/Kconfiglib/screenshots/screenshots/ss13.png
>
> The last screenshot shows how things might look after you jump to a
> symbol. The jumped-to symbol wasn't visible in this case, so show-all
> mode was turned on automatically.
Hi Ulf,
Do I need to save kconfiglib.py in a special location?
With (new) kconfiglib.py and menuconfig.py, I am getting this:
$ make ARCH=x86_64 O=xx64 iscriptconfig
make[1]: Entering directory '/home/rdunlap/lnx/lnx-417-rc3/xx64'
GEN ./Makefile
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named 'kconfiglib'
>>>
and then if I (being a Python novice) copy kconfiglib.py to
/usr/lib/python3.4/site-packages/ and try again, I get 16 warning messages (below)
and then this:
A Kconfig instance 'kconf' for the architecture x86_64 has been created.
>>>
What am I supposed to do now?
Hm, OK, I used the trick that you supplied a few weeks ago and I have the UI now.
ARCH=x86 SRCARCH=x86 KERNELVERSION=`make kernelversion` \
Kconfiglib/menuconfig.py
so yes, a real Makefile target would be nice. :)
thanks,
--
~Randy
the 16 warning messages:
warning: SCSI_DPT_I2O (defined at drivers/scsi/Kconfig:482) has leading or trailing whitespace in its prompt
warning: ATM_FIRESTREAM (defined at drivers/atm/Kconfig:149) has leading or trailing whitespace in its prompt
warning: IWLWIFI (defined at drivers/net/wireless/intel/iwlwifi/Kconfig:1) has leading or trailing whitespace in its prompt
warning: REGULATOR_MAX8973 (defined at drivers/regulator/Kconfig:479) has leading or trailing whitespace in its prompt
warning: MEMSTICK_TIFM_MS (defined at drivers/memstick/host/Kconfig:7) has leading or trailing whitespace in its prompt
warning: MV_XOR_V2 (defined at drivers/dma/Kconfig:374) has leading or trailing whitespace in its prompt
warning: PANEL_LCD_PIN_E (defined at drivers/auxdisplay/Kconfig:335) has leading or trailing whitespace in its prompt
warning: PANEL_LCD_PIN_RS (defined at drivers/auxdisplay/Kconfig:350) has leading or trailing whitespace in its prompt
warning: PANEL_LCD_PIN_RW (defined at drivers/auxdisplay/Kconfig:365) has leading or trailing whitespace in its prompt
warning: PANEL_LCD_PIN_SCL (defined at drivers/auxdisplay/Kconfig:380) has leading or trailing whitespace in its prompt
warning: PANEL_LCD_PIN_SDA (defined at drivers/auxdisplay/Kconfig:395) has leading or trailing whitespace in its prompt
warning: PANEL_LCD_PIN_BL (defined at drivers/auxdisplay/Kconfig:410) has leading or trailing whitespace in its prompt
warning: INTEGRITY_AUDIT (defined at security/integrity/Kconfig:54) has leading or trailing whitespace in its prompt
warning: the choice symbol VIRT_CPU_ACCOUNTING_GEN (defined at init/Kconfig:359) is selected by the following symbols, which has no effect:
- NO_HZ_FULL (defined at kernel/time/Kconfig:85)
warning: the choice symbol M486 (defined at arch/x86/Kconfig.cpu:53) is selected by the following symbols, which has no effect:
- X86_RDC321X (defined at arch/x86/Kconfig:653)
warning: the choice symbol FB_LITTLE_ENDIAN (defined at drivers/video/fbdev/Kconfig:168) is selected by the following symbols, which has no effect:
- FB_MB862XX_LIME (defined at drivers/video/fbdev/Kconfig:2190)
next prev parent reply other threads:[~2018-05-20 3:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 0:57 Ulf Magnusson
2018-05-01 17:56 ` Randy Dunlap
2018-05-01 18:13 ` Randy Dunlap
2018-05-01 18:52 ` Randy Dunlap
2018-05-01 19:33 ` Ulf Magnusson
2018-05-03 2:47 ` Ulf Magnusson
2018-05-03 20:31 ` Randy Dunlap
2018-05-03 21:26 ` Ulf Magnusson
2018-05-01 19:12 ` Ulf Magnusson
2018-05-01 19:47 ` Ulf Magnusson
2018-05-01 21:07 ` Ulf Magnusson
2018-05-03 20:28 ` Randy Dunlap
2018-05-03 22:48 ` Ulf Magnusson
2018-05-04 0:05 ` Randy Dunlap
2018-05-08 16:59 ` Ulf Magnusson
2018-05-11 1:22 ` Ulf Magnusson
2018-05-20 3:45 ` Randy Dunlap [this message]
2018-05-20 3:51 ` Randy Dunlap
2018-05-20 4:24 ` Ulf Magnusson
2018-05-20 5:50 ` Ulf Magnusson
2018-05-20 4:03 ` Randy Dunlap
2018-05-20 4:47 ` Ulf Magnusson
2018-05-20 5:13 ` Ulf Magnusson
2018-05-21 2:45 ` Randy Dunlap
2018-05-21 3:33 ` Ulf Magnusson
2018-05-21 3:47 ` Randy Dunlap
2018-05-22 10:18 ` Ulf Magnusson
2018-05-25 22:06 ` Randy Dunlap
2018-05-20 7:51 ` Ulf Magnusson
2018-05-21 2:22 ` Randy Dunlap
2018-05-20 6:03 ` Ulf Magnusson
2018-05-14 16:58 ` Pavel Machek
2018-05-14 18:12 ` Ulf Magnusson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4ec710f-b2bd-b9f0-c33a-159aa53ca73c@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ulfalizer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®