Hello there, On Tue, 8 Mar 2011 10:49:33 +0100, Michael Olbrich wrote: >> I Attached the Kconfig file and the two files included there. I hope >> it's okay to send it off list. You'll see we use this for our >> commercial product and I don't want to disclose internal >> information. Please keep it disclosed. >> >> What I just tried is: commenting out lines 33 to 35 in my Kconfig, >> so no other files are included. The error remains: >> >> adahl@vm-nra-ubuntu-10-4-dev ~/Work/src/bar.rootfs >> (git)-[master] % ptxdist-2011.02.0 migrate >> config/Kconfig:6: invalid statement >> >> ptxdist: 'ptx oldconfig' returned with an error > > back to the list... > > It looks like "mainmenu" can only be used in toplevel config file with the > latest kconfig. Just replace 'source "config/Kconfig"' with its content.
I didn't want to put all the content from /usr/local/lib/ptxdist-2011.02.0/config/Kconfig into my own config. What I did now was the following: I moved line 6 from the above mentioned file to my own 'Kconfig' in the root of my project folder, which looks (more or less) like this now: # # Kconfig: Main menu structure definition # Copyright (C) Juergen Beisert <[email protected]> 2008 # # first of all include toplevel Kconfig file as default mainmenu "PTXdist $CONFIGFILE_VERSION" source "config/Kconfig" # Note: This is the new ptxdist-2 mechanism: # # Create your *.in files and mark them in their header with a line like this: # # "## SECTION=project_specific" # # After that include this menu or menues with the following line: # # source "generated/project_specific.in" # # The SECTION name and the included file name here must be correspond. # You can use as many SECTIONs as you like, to add more than one local sub # menu. # # You can beautify the menu, when you are using: # # menu "Project Specific Menu " # source "generated/project_specific.in" # endmenu comment "----------- foo bar ------------" source "generated/foo.in" source "generated/bar.in" #comment "------------------------------------" AFAIR this is the suggested way to extend the menuconfig. I could successfully migrate the project then and it is currently rebuilding. :-) However changing a line in a file distributed by ptxdist or as suggested before copying stuff from there seems no perfect solution for me. In the first case I will run into a problem with the next update of ptxdist if the line in config/Kconfig remains. I assume I will get an error because of multiple lines starting with "mainmenu". The second case is even worse, because I would have to manually transplant changes in config/Kconfig with each update of ptxdist. Greets Alex -- ptxdist mailing list [email protected]
