Hello All, I am using the ptxdist version 1.99.11 and/or trunk(rev-9842) with the new collection config feature. 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. 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? 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? Kind Regards, Remy
my-testtools.in
Description: Binary data
-- ptxdist mailing list [email protected]
