Skip to contentSkip to conversation

can i totally ignore recipes not related to the current build?

DISCUSSION Robert P. J. Day 3 participants 6 messages Feb 22, 2020

lore
Share & tools
lore
#0 lore raw

i have a layer (from elsewhere) that needs massive migration, and
generates numerous parse errors, almost all related to a specialized image. my normal workflow is to try to build for an absolutely stock core-image-minimal, so i don't care about any recipes or .bbappends that don't contribute to that.

regardless (AIUI), all recipes in all included layers will at least
be *parsed* for syntactic correctness, even if they don't contribute to the final image, so i'd like a way to somehow totally ignore all processing of recipes that don't do that.

i'm aware of PNBLACKLIST, but i'm sure i verified that that simply
won't *build* that recipe, but it will still be parsed. is there a way to utterly ignore recipes that don't contribute to a given target? i'm sure there must be, i've just never had need for that until now.

rday

Signature · 7 lines
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                         http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================
#1 lore raw

BBMASK?

Alex

Quoted 34 lines · Robert P. J. Day

i have a layer (from elsewhere) that needs massive migration, and
generates numerous parse errors, almost all related to a specialized image. my normal workflow is to try to build for an absolutely stock core-image-minimal, so i don't care about any recipes or .bbappends that don't contribute to that.

regardless (AIUI), all recipes in all included layers will at least
be *parsed* for syntactic correctness, even if they don't contribute to the final image, so i'd like a way to somehow totally ignore all processing of recipes that don't do that.

i'm aware of PNBLACKLIST, but i'm sure i verified that that simply
won't *build* that recipe, but it will still be parsed. is there a way to utterly ignore recipes that don't contribute to a given target? i'm sure there must be, i've just never had need for that until now.

rday

--

========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday

========================================================================
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#2 lore raw
Quoted 1 line · Alexander Kanavin

BBMASK?

thank you. i knew there was something, i was just drawing a blank
and i can't remember the last time i needed to do that.

rday

#3 lore raw
In reply to Alexander Kanavin
Quoted 1 line · Alexander Kanavin

BBMASK?

BTW, that will work for me in this situation but is there a way to
not have to enumerate all the recipes to ignore, and just say, "don't look at anything that is not related to building core-image-minimal?" *that* would be seriously useful, because there's going to be a *ton* of recipes i need to ignore.

rday

#4 lore raw
Quoted 8 lines · Robert P. J. Day
Quoted 1 line · Alexander Kanavin

BBMASK?

BTW, that will work for me in this situation but is there a way to
not have to enumerate all the recipes to ignore, and just say, "don't look at anything that is not related to building core-image-minimal?"
...

How do you know without parsing that a recipe is not related? Information like names of packages built or RPROVIDES are in the recipes.

Quoted 1 line

rday

cu
Adrian

#5 lore raw
Quoted 5 lines · Adrian Bunk
Quoted 4 lines · Robert P. J. Day
Quoted 1 line · Alexander Kanavin

BBMASK?

Quoted 8 lines
Quoted 4 lines

BTW, that will work for me in this situation but is there a way to
not have to enumerate all the recipes to ignore, and just say, "don't look at anything that is not related to building core-image-minimal?"
...

How do you know without parsing that a recipe is not related? Information like names of packages built or RPROVIDES are in the recipes.

ah, good point ... i am not really thinking this through. duh.

rday