Re: [Ltib] Adding new package to configuration system

[Stuart Hughes]

Hi Andrea,

A good idea, but right now I just don't have any cycles spare.

Regards, Stuart

Andrea Galbusera wrote:
> Stuart,
> thank you a lot! Using the RIGHT names helps ;-) It works as expected
> now. Maybe I missed this but I'd suggest to document somewhere (maybe a
> FAQ?).
> 
> Regards
> Andrea
> 
> On Wed, 2010-03-17 at 14:41 +0000, Stuart Hughes wrote:
>> Hi Andrea,
>>
>> You won't need PKG_TPT2000_CVS as this is just a boolean and you'll only
>> be in that spec if it's set true.
>>
>> For PKG_TPT2000_CVS_TAG you'll need to rename it.  The reason is that
>> only certain names are exported in the environment automatically, this
>> is to reduce environmental pollution (and the possibility of a clash).
>>
>> The ones automatically exported must have the style:
>> _PRECONFIG, _WANT_ or SYSCFG_
>>
>> So I'd suggest in your case using:
>> PKG_TPT2000_WANT_CVS_TAG or PKG_TPT2000_CVS_TAG_PRECONFIG
>>
>> Regards, Stuart
>>
>> Andrea Galbusera wrote:
>>> Hi ltib folks,
>>> this is driving me crazy in the last hours. Hope it's not a silly
>>> question.
>>>
>>> Following guidelines in doc/LtibFaq I added a new package to the Package
>>> Selection List. Here is the relevant part in
>>> config/userspace/packages.lkc:
>>>
>>>> config PKG_TPT2000_CVS
>>>>     bool "tpt2000 software from CVS"
>>>>     default n
>>>>     help
>>>>     This package will include tpt2000 software as of the given CVS tag
>>>> into rootfs.
>>>>
>>>> config PKG_TPT2000_CVS_TAG
>>>>     depends PKG_TPT2000_CVS
>>>>     string "tpt2000 CVS tag to checkout"
>>>>     default "tpt_build_ng"
>>>>     help
>>>>     Put in the name of the tpt2000 CVS tag you want to build from.
>>> Both symbols get correctly into config/platform/mpc5121tpt/.config
>>>
>>>> $ grep PKG_TPT2000 config/platform/mpc5121tpt/.config
>>>> CONFIG_PKG_TPT2000_CVS=y
>>>> CONFIG_PKG_TPI2000_CVS_TAG="tpt_build_ng"
>>> I'd like to use the value assigned to PKG_TPT2000_CVS_TAG in my .spec
>>> file to drive custom build options (in this example the CVS tag to
>>> checkout), but I cannot get it to work. I mean either
>>> PKG_TPT2000_CVS_TAG or PKG_TPT2000_CVS appear to be undefined (empty
>>> string) within any section of my .spec file.
>>>
>>>> %Prep
>>>> echo "$PKG_TPT2000_CVS"
>>>> echo "$PKG_TPT2000_CVS_TAG"
>>> By looking at other .specs I guess this can be done. I also can
>>> succesfully access the value of other PKG_XXX symbols from within
>>> my .spec.
>>>
>>> What am I missing? How do symbols flow from configuration system
>>> to .spec files?
>>>
>>> TIA
>>> Andrea
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> LTIB home page: http://ltib.org
>>>
>>> Ltib mailing list
>>> address@hidden
>>> http://lists.nongnu.org/mailman/listinfo/ltib
>>>
> 
>