On Wed, Feb 25, 2009 at 10:01:40PM +0100, Remy Bohmer wrote:
> I am using the ptxdist version 1.99.11 and/or trunk(rev-9842) with the
> new collection config feature.
Ah, great!
> What I am trying to achieve here is to build 2 configurations out of 1
> userland ptxconfig file, namely a small-release image, and a
> full-blown debug-image.
It was invented for such scenarios.
> Packages that only need to go to the debug image are marked as 'Module'.
>
> Basically it works as I expected, however there are some weird things
> happening.
> I have a project-specific-rules-file (see attached) outside of ptxdist
> in the rules directory of the project. ptxdist fully understand it and
> it is working properly in the 'normal' menus and during build time, as
> long as I do not use the collection mechanism.
>
> If I use the collection mechanism, the entries marked as module in
> this rule file are not visible in 'ptxdist menuconfig collection'.
> If I make the 1st entry tristate, only that element is selectable in
> the menu. If I move the MY_TESTTOOLS_TOOL1 (and the other) config
> options outside the if-statement, still only the 1st entry is visible.
> Apparently the collection/module entries are parsed in a special way,
> but I have not figured out how exactly.
>
> So, I am trying to debug this problem, but I have not found the cause
> yet. Anyone any idea?
You need to make the *packet* tristate, not the feature-options in the
"if" part. There is some magic that correlates the packet labels (name
in capital letters) to the packet names. So instead of your ...
-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----
## SECTION=applications
menuconfig MY_TESTTOOLS
bool
prompt "Testtools"
help
All testtools that need cross compilation to the target.
if MY_TESTTOOLS
config MY_TESTTOOLS_TOOL1
tristate
prompt "Tool 1"
config MY_TESTTOOLS_TOOL2
tristate
prompt "Tool 2"
config MY_TESTTOOLS_TOOL3
tristate
prompt "Tool 3"
endif
-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----
you should make one in file per application and, if you want to, put
them into your own section, like
-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----
## SECTION=project_specific
menuconfig MY_TESTTOOLS_TOOL1
tristate
prompt "Tool 1"
if MY_TESTTOOLS_TOOL1
...
endif
-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----8<-----
The "project_specific" section is included by default, if you want to
use your own section (maybe for grouping the test tools like you
mentioned above), invent one and put something like
source "generated/my_section.in"
into one of the already included Kconfig files.
> BTW: I also have some patches on top of trunk, like for example:
> * Adding support for AT91 Bootstrap code for booting via bootROM from
> dataflash/nandflash on at91sam926x cores.
> * Make DTC (device tree compiler) version configurable, to be able to
> build FIT images for U-boot
> * Build libusb-compat-0.1 on top of libusb-1.0.
> * Use (configurable) newer version of U-boot mkimage (upgrade from
> 1.1.6 to 2009.01 to be able to build FIT-images, requires DTC v1.2.0)
>
> Anyone interested?
Yes, just send them to the mailing list!
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
[email protected]
