Skip to contentSkip to conversation

adjust BBPATH to be a good citizen of layer world

PATCH In review Khem Raj 3 participants 14 messages Nov 7, 2013

lore
Share & tools
lore

Khem Raj

author
#0 lore raw

PATCH 1/1 adjust BBPATH to be a good citizen of layer world

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
 conf/layer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES
 BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
Signature · 1 line
1.8.3.2
#1 lore raw

This seems like a reversal of http://arago-project.org/git/meta-ti.git?a=commit;h=dabd83e96fe99d0c3d1a88be4d1637831526d217

Looks like there may be a need to cover the different use cases and understand what each person is trying to do :)

Quoted 37 lines

-----Original Message-----
From: [email protected] [mailto:meta-ti- [email protected]] On Behalf Of Khem Raj
Sent: Thursday, November 07, 2013 7:55 AM
To: [email protected]
Subject: [meta-ti] [PATCH] adjust BBPATH to be a good citizen of layer world

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
--
1.8.3.2

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

author
#2 lore raw
Quoted 4 lines · Chase

This seems like a reversal of http://arago-project.org/git/meta-ti.git?a=commit;h=dabd83e96fe99d0c3d1a88be4d1637831526d217

Looks like there may be a need to cover the different use cases and understand what each person is trying to do :)

ah I see what caused this all pain. So now meta-ti is odd ball out. this patch should have never gone in.

Quoted 37 lines
Quoted 37 lines

-----Original Message-----
From: [email protected] [mailto:meta-ti- [email protected]] On Behalf Of Khem Raj
Sent: Thursday, November 07, 2013 7:55 AM
To: [email protected]
Subject: [meta-ti] [PATCH] adjust BBPATH to be a good citizen of layer world

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
--
1.8.3.2

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

#3 lore raw
Quoted 9 lines · Khem Raj
Quoted 5 lines · Chase

This seems like a reversal of http://arago-project.org/git/meta-ti.git?a=commit;h=dabd83e96fe99d0c3d1a88be4d1637831526d217

Looks like there may be a need to cover the different use cases and understand what each person is trying to do :)

ah I see what caused this all pain. So now meta-ti is odd ball out. this patch should have never gone in.

Khem,

If you remember, we discussed this with Richard and he suggested this as a solution to the ordering problem. Otherwise people tend to append any extra layers _after_ oe-core, which should be the other way around in order to override anything in there...

Signature · 1 line
Denys
Quoted 41 lines
Quoted 33 lines
Quoted 33 lines

-----Original Message-----
From: [email protected] [mailto:meta-ti- [email protected]] On Behalf Of Khem Raj
Sent: Thursday, November 07, 2013 7:55 AM
To: [email protected]
Subject: [meta-ti] [PATCH] adjust BBPATH to be a good citizen of layer world

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
--
1.8.3.2

Quoted 4 lines
Quoted 4 lines

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

author
#4 lore raw
Quoted 11 lines · Denys Dmytriyenko
Quoted 9 lines · Khem Raj
Quoted 5 lines · Chase

This seems like a reversal of http://arago-project.org/git/meta-ti.git?a=commit;h=dabd83e96fe99d0c3d1a88be4d1637831526d217

Looks like there may be a need to cover the different use cases and understand what each person is trying to do :)

ah I see what caused this all pain. So now meta-ti is odd ball out. this patch should have never gone in.

Quoted 6 lines

Khem,

If you remember, we discussed this with Richard and he suggested this as a solution to the ordering problem. Otherwise people tend to append any extra layers _after_ oe-core, which should be the other way around in order to override anything in there…

I think the problem is when you have many other layers then the whole paradigm changes to it and you end up with same issue upside down. I think how you order bblayer.conf can control the override of oe-core, I wish if distro’s could control the layer.conf for each bsp layer then it wouldnt matter as much

Quoted 46 lines
Signature · 2 lines
-- 
Denys
Quoted 41 lines
Quoted 33 lines
Quoted 33 lines

-----Original Message-----
From: [email protected] [mailto:meta-ti- [email protected]] On Behalf Of Khem Raj
Sent: Thursday, November 07, 2013 7:55 AM
To: [email protected]
Subject: [meta-ti] [PATCH] adjust BBPATH to be a good citizen of layer world

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
--
1.8.3.2

Quoted 4 lines
Quoted 4 lines

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

#5 lore raw
Quoted 21 lines · Khem Raj
Quoted 11 lines · Denys Dmytriyenko
Quoted 9 lines · Khem Raj
Quoted 5 lines · Chase

This seems like a reversal of http://arago-project.org/git/meta-ti.git?a=commit;h=dabd83e96fe99d0c3d1a88be4d1637831526d217

Looks like there may be a need to cover the different use cases and understand what each person is trying to do :)

ah I see what caused this all pain. So now meta-ti is odd ball out. this patch should have never gone in.

Quoted 6 lines

Khem,

If you remember, we discussed this with Richard and he suggested this as a solution to the ordering problem. Otherwise people tend to append any extra layers _after_ oe-core, which should be the other way around in order to override anything in there…

Quoted 5 lines

I think the problem is when you have many other layers then the whole paradigm changes to it and you end up with same issue upside down. I think how you order bblayer.conf can control the override of oe-core, I wish if distro’s could control the layer.conf for each bsp layer then it wouldnt matter as much

I agree this is a bigger issue. I looked at some layers and found few that prepend themselves, while most of others just append.

The order inside bblayers.conf is much more important than people let to believe. For example, if multiple layers define the machine config, the first one listed in bblayers.conf wins - this is a real problem for beagleboard.conf that is currently being defined in meta-ti as well as meta-yocto-bsp (as a reference platform) and meta-beagleboard too. Very soon the same problem will happen to beaglebone.conf, when meta-yocto-bsp picks it up as a reference...

Anyway, the biggest issue I'm trying to work around with this change is the "shadowing" of the new-style DTBs that I ported from Dora to Dylan. If meta-ti is not in front of oe-core, the old-style DTBs come into play and DTBs are not built at all. So, this is not really an issue for Dora or master, and those don't need to be prepended after all...

Quoted 42 lines
Quoted 41 lines
Quoted 41 lines
Quoted 33 lines
Quoted 33 lines

-----Original Message-----
From: [email protected] [mailto:meta-ti- [email protected]] On Behalf Of Khem Raj
Sent: Thursday, November 07, 2013 7:55 AM
To: [email protected]
Subject: [meta-ti] [PATCH] adjust BBPATH to be a good citizen of layer world

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
--
1.8.3.2

Quoted 4 lines
Quoted 4 lines

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

author
#6 lore raw
Quoted 38 lines · Denys Dmytriyenko
Quoted 21 lines · Khem Raj
Quoted 11 lines · Denys Dmytriyenko
Quoted 9 lines · Khem Raj
Quoted 5 lines · Chase

This seems like a reversal of http://arago-project.org/git/meta-ti.git?a=commit;h=dabd83e96fe99d0c3d1a88be4d1637831526d217

Looks like there may be a need to cover the different use cases and understand what each person is trying to do :)

ah I see what caused this all pain. So now meta-ti is odd ball out. this patch should have never gone in.

Quoted 6 lines

Khem,

If you remember, we discussed this with Richard and he suggested this as a solution to the ordering problem. Otherwise people tend to append any extra layers _after_ oe-core, which should be the other way around in order to override anything in there…

Quoted 5 lines

I think the problem is when you have many other layers then the whole paradigm changes to it and you end up with same issue upside down. I think how you order bblayer.conf can control the override of oe-core, I wish if distro’s could control the layer.conf for each bsp layer then it wouldnt matter as much

I agree this is a bigger issue. I looked at some layers and found few that prepend themselves, while most of others just append.

The order inside bblayers.conf is much more important than people let to believe. For example, if multiple layers define the machine config, the first one listed in bblayers.conf wins - this is a real problem for beagleboard.conf that is currently being defined in meta-ti as well as meta-yocto-bsp (as a reference platform) and meta-beagleboard too. Very soon the same problem will happen to beaglebone.conf, when meta-yocto-bsp picks it up as a reference...

Quoted 5 lines

Anyway, the biggest issue I'm trying to work around with this change is the "shadowing" of the new-style DTBs that I ported from Dora to Dylan. If meta-ti is not in front of oe-core, the old-style DTBs come into play and DTBs are not built at all. So, this is not really an issue for Dora or master, and those don't need to be prepended after all…

Now its even more intriguing since you changed meta-ti/master and I would have expected this change to show up in meta-ti/dylan or are you claiming all sort of oe-core branches to work with meta-ti/master thats a perilous path.

Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 35 lines
Quoted 35 lines

-----Original Message-----
From: [email protected][mailto:meta-ti- [email protected]] On Behalf Of Khem Raj
Sent: Thursday, November 07, 2013 7:55 AM
To: [email protected]
Subject: [meta-ti] [PATCH] adjust BBPATH to be a good citizen of layer world

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
--
1.8.3.2

Quoted 4 lines
Quoted 4 lines

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

#7 lore raw
Quoted 48 lines · Khem Raj
Quoted 38 lines · Denys Dmytriyenko
Quoted 21 lines · Khem Raj
Quoted 11 lines · Denys Dmytriyenko
Quoted 9 lines · Khem Raj
Quoted 5 lines · Chase

This seems like a reversal of http://arago-project.org/git/meta-ti.git?a=commit;h=dabd83e96fe99d0c3d1a88be4d1637831526d217

Looks like there may be a need to cover the different use cases and understand what each person is trying to do :)

ah I see what caused this all pain. So now meta-ti is odd ball out. this patch should have never gone in.

Quoted 6 lines

Khem,

If you remember, we discussed this with Richard and he suggested this as a solution to the ordering problem. Otherwise people tend to append any extra layers _after_ oe-core, which should be the other way around in order to override anything in there…

Quoted 5 lines

I think the problem is when you have many other layers then the whole paradigm changes to it and you end up with same issue upside down. I think how you order bblayer.conf can control the override of oe-core, I wish if distro’s could control the layer.conf for each bsp layer then it wouldnt matter as much

I agree this is a bigger issue. I looked at some layers and found few that prepend themselves, while most of others just append.

The order inside bblayers.conf is much more important than people let to believe. For example, if multiple layers define the machine config, the first one listed in bblayers.conf wins - this is a real problem for beagleboard.conf that is currently being defined in meta-ti as well as meta-yocto-bsp (as a reference platform) and meta-beagleboard too. Very soon the same problem will happen to beaglebone.conf, when meta-yocto-bsp picks it up as a reference...

Quoted 5 lines

Anyway, the biggest issue I'm trying to work around with this change is the "shadowing" of the new-style DTBs that I ported from Dora to Dylan. If meta-ti is not in front of oe-core, the old-style DTBs come into play and DTBs are not built at all. So, this is not really an issue for Dora or master, and those don't need to be prepended after all…

Quoted 4 lines

Now its even more intriguing since you changed meta-ti/master and I would have expected this change to show up in meta-ti/dylan or are you claiming all sort of oe-core branches to work with meta-ti/master thats a perilous path.

It's in meta-ti/dylan AND meta-ti/master, as I thought the change was rather safe. But what I'm saying now is that it's not really needed in meta-ti/master, only dylan.

As of meta-ti/master, it should work with oe-core/master and maybe dora, but probably it's time to branch of meta-ti/dora, since there were some changes in oe-core/master no longer compatible with dora...

Quoted 42 lines
Quoted 41 lines
Quoted 41 lines
Quoted 41 lines
Quoted 41 lines
Quoted 33 lines
Quoted 33 lines

-----Original Message-----
From: [email protected][mailto:meta-ti- [email protected]] On Behalf Of Khem Raj
Sent: Thursday, November 07, 2013 7:55 AM
To: [email protected]
Subject: [meta-ti] [PATCH] adjust BBPATH to be a good citizen of layer world

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
--
1.8.3.2

Quoted 4 lines
Quoted 4 lines

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

author
#8 lore raw
Quoted 49 lines · Denys Dmytriyenko
Quoted 48 lines · Khem Raj
Quoted 43 lines · Denys Dmytriyenko
Quoted 21 lines · Khem Raj
Quoted 11 lines · Denys Dmytriyenko
Quoted 9 lines · Khem Raj
Quoted 5 lines · Chase

This seems like a reversal of http://arago-project.org/git/meta-ti.git?a=commit;h=dabd83e96fe99d0c3d1a88be4d1637831526d217

Looks like there may be a need to cover the different use cases and understand what each person is trying to do :)

ah I see what caused this all pain. So now meta-ti is odd ball out. this patch should have never gone in.

Quoted 6 lines

Khem,

If you remember, we discussed this with Richard and he suggested this as a solution to the ordering problem. Otherwise people tend to append any extra layers _after_ oe-core, which should be the other way around in order to override anything in there…

Quoted 5 lines

I think the problem is when you have many other layers then the whole paradigm changes to it and you end up with same issue upside down. I think how you order bblayer.conf can control the override of oe-core, I wish if distro’s could control the layer.conf for each bsp layer then it wouldnt matter as much

I agree this is a bigger issue. I looked at some layers and found few that prepend themselves, while most of others just append.

The order inside bblayers.conf is much more important than people let to believe. For example, if multiple layers define the machine config, the first one listed in bblayers.conf wins - this is a real problem for beagleboard.conf that is currently being defined in meta-ti as well as meta-yocto-bsp (as a reference platform) and meta-beagleboard too. Very soon the same problem will happen to beaglebone.conf, when meta-yocto-bsp picks it up as a reference...

Anyway, the biggest issue I'm trying to work around with this change is the "shadowing" of the new-style DTBs that I ported from Dora to Dylan. If meta-ti is not in front of oe-core, the old-style DTBs come into play and DTBs are not built at all. So, this is not really an issue for Dora or master, and those don't need to be prepended after all…

Quoted 6 lines
Quoted 4 lines

Now its even more intriguing since you changed meta-ti/master and I would have expected this change to show up in meta-ti/dylan or are you claiming all sort of oe-core branches to work with meta-ti/master thats a perilous path.

It's in meta-ti/dylan AND meta-ti/master,

yes. So can we change the master please ?
oe-core is also appending itself in BBPATH in oe-core/master and so are meta-yocto-bsp and meta-beagleboard so with mere ordering of these layers in your distro’s bblayer.conf you should be able to get desired behaviour.

Quoted 7 lines

as I thought the change was
rather safe. But what I'm saying now is that it's not really needed in meta-ti/master, only dylan.

As of meta-ti/master, it should work with oe-core/master and maybe dora, but probably it's time to branch of meta-ti/dora, since there were some changes in oe-core/master no longer compatible with dora…

sure yes but have that commit before you branch out.

Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 35 lines
Quoted 35 lines

-----Original Message-----
From: [email protected][mailto:meta-ti- [email protected]] On Behalf Of Khem Raj
Sent: Thursday, November 07, 2013 7:55 AM
To: [email protected]
Subject: [meta-ti] [PATCH] adjust BBPATH to be a good citizen of layer world

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
--
1.8.3.2

Quoted 4 lines
Quoted 4 lines

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

#9 lore raw
Quoted 52 lines · Khem Raj
Quoted 49 lines · Denys Dmytriyenko
Quoted 48 lines · Khem Raj
Quoted 43 lines · Denys Dmytriyenko
Quoted 21 lines · Khem Raj
Quoted 11 lines · Denys Dmytriyenko
Quoted 9 lines · Khem Raj
Quoted 5 lines · Chase

This seems like a reversal of http://arago-project.org/git/meta-ti.git?a=commit;h=dabd83e96fe99d0c3d1a88be4d1637831526d217

Looks like there may be a need to cover the different use cases and understand what each person is trying to do :)

ah I see what caused this all pain. So now meta-ti is odd ball out. this patch should have never gone in.

Quoted 6 lines

Khem,

If you remember, we discussed this with Richard and he suggested this as a solution to the ordering problem. Otherwise people tend to append any extra layers _after_ oe-core, which should be the other way around in order to override anything in there…

Quoted 5 lines

I think the problem is when you have many other layers then the whole paradigm changes to it and you end up with same issue upside down. I think how you order bblayer.conf can control the override of oe-core, I wish if distro’s could control the layer.conf for each bsp layer then it wouldnt matter as much

I agree this is a bigger issue. I looked at some layers and found few that prepend themselves, while most of others just append.

The order inside bblayers.conf is much more important than people let to believe. For example, if multiple layers define the machine config, the first one listed in bblayers.conf wins - this is a real problem for beagleboard.conf that is currently being defined in meta-ti as well as meta-yocto-bsp (as a reference platform) and meta-beagleboard too. Very soon the same problem will happen to beaglebone.conf, when meta-yocto-bsp picks it up as a reference...

Anyway, the biggest issue I'm trying to work around with this change is the "shadowing" of the new-style DTBs that I ported from Dora to Dylan. If meta-ti is not in front of oe-core, the old-style DTBs come into play and DTBs are not built at all. So, this is not really an issue for Dora or master, and those don't need to be prepended after all…

Quoted 8 lines
Quoted 6 lines
Quoted 4 lines

Now its even more intriguing since you changed meta-ti/master and I would have expected this change to show up in meta-ti/dylan or are you claiming all sort of oe-core branches to work with meta-ti/master thats a perilous path.

It's in meta-ti/dylan AND meta-ti/master,

yes. So can we change the master please ?

I'll think about it ;)

Quoted 1 line

oe-core is also appending itself in BBPATH in oe-core/master

Yes, I know.

Quoted 1 line

and so are meta-yocto-bsp and meta-beagleboard

Also quite aware of that.

But since you mention meta-yocto-bsp, which is part of Poky, do you know that meta-yocto prepends itself in front? And I believe there were one or two more obscure layers doing that as well...

BTW, I like the comment you made in meta-oe long time ago:

# It really depends on order of the layers appearing in BBLAYERS

# variable in toplevel bblayers.conf file, where bitbake will search
# for .inc files and others where bitbake uses BBPATH since it will
# search the directories from first to last as specified in BBPATH
# Therefore if you want a given layer to be considered high priority
# for the .inc and .conf etc. then consider it adding at the beginning
# of BBPATH. For bblayers bitbake will use BBFILES_PRIORITY to resolve
# the recipe contention so the order of directories in BBFILES does 
# not matter.

But the problem is that people don't read comments and don't bother with BBLAYERS order, hence I had to do what you suggested above with BBPATH order instead!

Quoted 2 lines

so with mere ordering of these layers in your distro’s bblayer.conf you should be able to get desired behaviour.

Well, it's not really a problem for Arago or Angstrom, as both provide setup tools to generate the correct bblayers.conf with the proper order of BBLAYERS. But the problem is really with Poky, as it expects people to manually add extra layers to bblayers.conf and people just tend to append everything AFTER oe-core and meta-yocto and meta-yocto-bsp. So, it's really Poky that is broken or rather unclear...

Quoted 54 lines
Quoted 7 lines

as I thought the change was
rather safe. But what I'm saying now is that it's not really needed in meta-ti/master, only dylan.

As of meta-ti/master, it should work with oe-core/master and maybe dora, but probably it's time to branch of meta-ti/dora, since there were some changes in oe-core/master no longer compatible with dora…

sure yes but have that commit before you branch out.

Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 35 lines
Quoted 35 lines

-----Original Message-----
From: [email protected][mailto:meta-ti- [email protected]] On Behalf Of Khem Raj
Sent: Thursday, November 07, 2013 7:55 AM
To: [email protected]
Subject: [meta-ti] [PATCH] adjust BBPATH to be a good citizen of layer world

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
--
1.8.3.2

Quoted 4 lines
Quoted 4 lines

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

author
#10 lore raw
Quoted 70 lines · Denys Dmytriyenko
Quoted 52 lines · Khem Raj
Quoted 49 lines · Denys Dmytriyenko
Quoted 48 lines · Khem Raj
Quoted 43 lines · Denys Dmytriyenko
Quoted 21 lines · Khem Raj
Quoted 11 lines · Denys Dmytriyenko
Quoted 9 lines · Khem Raj
Quoted 5 lines · Chase

This seems like a reversal of http://arago-project.org/git/meta-ti.git?a=commit;h=dabd83e96fe99d0c3d1a88be4d1637831526d217

Looks like there may be a need to cover the different use cases and understand what each person is trying to do :)

ah I see what caused this all pain. So now meta-ti is odd ball out. this patch should have never gone in.

Quoted 6 lines

Khem,

If you remember, we discussed this with Richard and he suggested this as a solution to the ordering problem. Otherwise people tend to append any extra layers _after_ oe-core, which should be the other way around in order to override anything in there…

Quoted 5 lines

I think the problem is when you have many other layers then the whole paradigm changes to it and you end up with same issue upside down. I think how you order bblayer.conf can control the override of oe-core, I wish if distro’s could control the layer.conf for each bsp layer then it wouldnt matter as much

I agree this is a bigger issue. I looked at some layers and found few that prepend themselves, while most of others just append.

The order inside bblayers.conf is much more important than people let to believe. For example, if multiple layers define the machine config, the first one listed in bblayers.conf wins - this is a real problem for beagleboard.conf that is currently being defined in meta-ti as well as meta-yocto-bsp (as a reference platform) and meta-beagleboard too. Very soon the same problem will happen to beaglebone.conf, when meta-yocto-bsp picks it up as a reference...

Anyway, the biggest issue I'm trying to work around with this change is the "shadowing" of the new-style DTBs that I ported from Dora to Dylan. If meta-ti is not in front of oe-core, the old-style DTBs come into play and DTBs are not built at all. So, this is not really an issue for Dora or master, and those don't need to be prepended after all…

Quoted 8 lines
Quoted 6 lines
Quoted 4 lines

Now its even more intriguing since you changed meta-ti/master and I would have expected this change to show up in meta-ti/dylan or are you claiming all sort of oe-core branches to work with meta-ti/master thats a perilous path.

It's in meta-ti/dylan AND meta-ti/master,

yes. So can we change the master please ?

I'll think about it ;)

Quoted 1 line

oe-core is also appending itself in BBPATH in oe-core/master

Yes, I know.

Quoted 7 lines
Quoted 1 line

and so are meta-yocto-bsp and meta-beagleboard

Also quite aware of that.

But since you mention meta-yocto-bsp, which is part of Poky, do you know that meta-yocto prepends itself in front? And I believe there were one or two more obscure layers doing that as well…

we can coerce them to change as well. if I have time I will go through this on layers index. Its good in general to have this since its beneficial and does larger good.

Quoted 13 lines

BTW, I like the comment you made in meta-oe long time ago:

# It really depends on order of the layers appearing in BBLAYERS

# variable in toplevel bblayers.conf file, where bitbake will search
# for .inc files and others where bitbake uses BBPATH since it will
# search the directories from first to last as specified in BBPATH
# Therefore if you want a given layer to be considered high priority
# for the .inc and .conf etc. then consider it adding at the beginning
# of BBPATH. For bblayers bitbake will use BBFILES_PRIORITY to resolve
# the recipe contention so the order of directories in BBFILES does 
# not matter.
Quoted 3 lines

But the problem is that people don't read comments and don't bother with BBLAYERS order, hence I had to do what you suggested above with BBPATH order instead!

amen

Quoted 11 lines
Quoted 4 lines

so with mere ordering of these layers in your distro’s bblayer.conf you should be able to get desired behaviour.

Well, it's not really a problem for Arago or Angstrom, as both provide setup tools to generate the correct bblayers.conf with the proper order of BBLAYERS. But the problem is really with Poky, as it expects people to manually add extra layers to bblayers.conf and people just tend to append everything AFTER oe-core and meta-yocto and meta-yocto-bsp. So, it's really Poky that is broken or rather unclear…

yes and I think as long as all layers follow append model it will bring some santiy to poky model as well.

#11 lore raw
In reply to Khem Raj

NAK for now, as there was a chance to comment on the proposed change:

http://thread.gmane.org/gmane.linux.embedded.yocto.meta-ti/2939

Quoted 28 lines · Khem Raj

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
 conf/layer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES
 BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
Signature · 6 lines
1.8.3.2

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti
author
#12 lore raw
Quoted 1 line · Denys Dmytriyenko

NAK for now, as there was a chance to comment on the proposed change:

well. I did not try, that change however its not that its set in stone either.
now meta-ti appears appears first no matter what in angstrom
in BBPATH and shadows meta-beagleboard which also provides definitions for beaglebone.conf which I want to use and no matter what I try unless I start changing the other layers to prepend as well I do not get the right order. I can happily punt out meta-ti or fork it but thats not the solution I am looking for.

Quoted 32 lines

http://thread.gmane.org/gmane.linux.embedded.yocto.meta-ti/2939

Quoted 28 lines · Khem Raj

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"

Signature · 6 lines
1.8.3.2

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti
#13 lore raw
Quoted 5 lines · Khem Raj
Quoted 1 line · Denys Dmytriyenko

NAK for now, as there was a chance to comment on the proposed change:

Quoted 7 lines

well. I did not try, that change however its not that its set in stone either. now meta-ti appears appears first no matter what in angstrom in BBPATH and shadows meta-beagleboard which also provides definitions for beaglebone.conf which I want to use and no matter what I try unless I start changing the other layers to prepend as well I do not get the right order. I can happily punt out meta-ti or fork it but thats not the solution I am looking for.

Indeed - one of the problems I just described in the other reply to this thread.

Anyway, what really bothers me, is that you, me and Richard had this exact discussion at ELCE and agreed that prepending should solve the issue... :)

Quoted 32 lines
Quoted 31 lines

http://thread.gmane.org/gmane.linux.embedded.yocto.meta-ti/2939

Quoted 28 lines · Khem Raj

Currently, meta-ti appears as first path in BBPATH rest of layers append so lets do the same

helps distros with multiple BSP layers to include meta-ti

---
conf/layer.conf | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)
conf/layer.conf +1 -1
index e39bd85..faa4ac0 100644
@@ -1,5 +1,5 @@
 # We have a conf and classes directory, append to BBPATH
-BBPATH =. "${LAYERDIR}:"
+BBPATH .= ":${LAYERDIR}"
 
 # We have a recipes directory, add to BBFILES

BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"

Signature · 6 lines
1.8.3.2

_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti