Jon,
If you want to test the change, you can use the wip branch to run a
build and make sure that everything is back to the way it was.
On 2/20/2025 5:09 PM, Ryan Eatmon via lists.yoctoproject.org wrote:
On 2/20/2025 1:19 PM, Jon Cormier wrote:
On Thu, Feb 20, 2025 at 12:59 PM Ryan Eatmon <[email protected]> wrote:
Having refreshed my memory from that time...
I auto converted OEBASE to TOPDIR because OEBASE is not a defined
variable. I'm not sure what the history of that variable was, but it is
not being set by any tool in the bitbake universe that I could find. So
before the conversion that was just getting expanded to "".
So it looks like OEBASE is setup by the oe-layersetup script and gets
inserted into the build/conf/setenv file:
Doh. All of my searches for OEBASE did not include the setup script
itself... That's on me. But I do think that moving to values relative
to TOPDIR instead of OEBASE will be better in the long run.
setenv:
# Set OEBASE to where the build and source directories reside
# NOTE: Do NOT place a trailing / on the end of OEBASE.
export OEBASE="/work"
...
This presumably wouldn't work for the other config systems (kas,
bitbake-setup, etc) since they don't run oe-layersetup...
Where as TOPDIR is a defined variable in bitbake that points to the dir
where the build was launched from.
I didn't even think of it being a side effect, I was just fixing
something that seemed broken. Our build scripts are explicitly setting
DL_DIR and SSTATE_DIR because the scripts need to upload the files in
those dirs to our NAS for better reuse, so we were not impacted by this
change.
Hmm thats a interesting, unrelated: I currently network share our
SSTATE_DIR but don't do it for DL_DIR, I just rsync it at the end of
the build. Do you host your own BB_HASHSERVE and PRSERV?
We rsync both the downloads and sstate to a NAS that all of our build
servers can access. Yes, we run our own BB_HASHSERVE and PRSERV so that
all of the build jobs are aligned on what the values for the PR should be.
I can change it back if people want it, but OEBASE is not even really a
variable as far as I can tell.
Or I could change it to:
DL_DIR = "${TOPDIR}/../downloads"
SSTATE_DIR = "${TOPDIR}/sstate-cache"
Does that match the previous behavior?
It does look like TOPDIR points to the build directory instead of one
directory up like before. sstate-cache is currently being put in
build/build/sstate-cache
jcormier@jcormier-MS-7A93:/export/space/jcormier/yocto/yocto_scarthgap/oe-layersetup$
ls build/
arago-tmp-default-baremetal-k3r5 build conf
arago-tmp-default-glibc buildhistory deploy-ti
bitbake-cookerdaemon.log cache downloads
jcormier@jcormier-MS-7A93:/export/space/jcormier/yocto/yocto_scarthgap/oe-layersetup$
ls build/build
sstate-cache
Any preferences?
I assume keeping OEBASE isn't an option since it won't exist for these
other setup systems. So I guess your second option.
Ok. I'll post a patch and make this change.
On 2/20/2025 10:58 AM, Jon Cormier wrote:
After build processor-sdk-scarthgap-chromium-10.01.10.04-config, I
noticed the downloads directory has moved to the build/downloads
folder,
instead of being at the top of the build directory. Was this
intentional? I suspect it probably happened when everything was
converted to xml configs. But the commit doesn't mention that as a
known
side effect.
commit aea8e0f53cb05e2d80056b3568f3376741c90853
Author: Ryan Eatmon <[email protected] <mailto:[email protected]>>
Date: Thu Oct 10 11:43:57 2024 -0500
Initial conversion of new XML configs
...
-DL_DIR = "${OEBASE}/downloads"
+DL_DIR = "${TOPDIR}/downloads"
...
-SSTATE_DIR = "${OEBASE}/build/sstate-cache"
+SSTATE_DIR = "${TOPDIR}/build/sstate-cache"
SSTATE_DIR was also updated and it still looks to be put in the same
place as ever...
On Thu, Dec 19, 2024 at 11:34 AM Chirag Shilwant via
lists.yoctoproject.org <http://lists.yoctoproject.org>
<[email protected]
<mailto:[email protected]>> wrote:
- Add processor-sdk-scarthgap-10.01.10.04-config used for
building AM62SIP & AM64x.
- Add processor-sdk-scarthgap-chromium-10.01.10.04-config
used for building AM62P, AM62x, AM62LP & Beagleplay.
Signed-off-by: Chirag Shilwant <[email protected]
<mailto:[email protected]>>
---
...
--
Jonathan Cormier
Senior Software Engineer
Voice: 315.425.4045 x222
http://www.CriticalLink.com <http://www.criticallink.com/>
6712 Brooklawn Parkway, Syracuse, NY 13211
<https://twitter.com/Critical_Link>
--
Ryan Eatmon [email protected]
-----------------------------------------
Texas Instruments, Inc. - LCPD - MGTS
--
Ryan Eatmon [email protected]
-----------------------------------------
Texas Instruments, Inc. - LCPD - MGTS
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#15884):
https://lists.yoctoproject.org/g/meta-arago/message/15884
Mute This Topic: https://lists.yoctoproject.org/mt/110200559/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-arago/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
