Correct build folder location

Correct build folder location

[Electronic Consult]

[-- Attachment #1: Type: text/plain, Size: 4165 bytes --]

Hello all,

I'm using Dunfell & up to know I've being using meta-atmel to build images.
I'd like to now add the capability to build images using meta-raspberrypi
but I'm having issues with the source oe-init-build-env step, it keeps
pulling in the meta-atmel shell environment. My folder layout is below. As
per meta-atmel instructions <https://github.com/linux4sam/meta-atmel> I put
build-microchip in the poky directory, as per meta-raspberrypi I put
rpi-build directory in parallel with the poky directory.

Which is correct?
Could this be causing the issue?

Thanks,

Owen

```
.
├── ChangeLog
├── localCache
│   ├── downloads
│   ├── setup.txt
│   └── sstate-cache
├── meta-atmel
│   ├── conf
│   ├── COPYING.MIT
│   ├── dynamic-layers
│   ├── flashing.txt
│   ├── licenses
│   ├── README
│   ├── recipes-atmel
│   ├── recipes-bsp
│   ├── recipes-connectivity
│   ├── recipes-core
│   ├── recipes-devtools
│   ├── recipes-egt
│   ├── recipes-graphics
│   ├── recipes-kernel
│   ├── recipes-multimedia
│   ├── recipes-security
│   ├── recipes-support
│   ├── recipes-utils
│   └── scripts
├── meta-aws
│   ├── CODE_OF_CONDUCT.md
│   ├── conf
│   ├── CONTRIBUTING.md
│   ├── images
│   ├── LICENSE
│   ├── qa
│   ├── README.md
│   ├── recipes-cloud
│   ├── recipes-devtools
│   ├── recipes-external
│   ├── recipes-iot
│   ├── recipes-multimedia
│   ├── recipes-neo-ai
│   ├── recipes-sdk
│   └── recipes-support
├── meta-openembedded
│   ├── contrib
│   ├── COPYING.MIT
│   ├── meta-filesystems
│   ├── meta-gnome
│   ├── meta-initramfs
│   ├── meta-multimedia
│   ├── meta-networking
│   ├── meta-oe
│   ├── meta-perl
│   ├── meta-python
│   ├── meta-webserver
│   ├── meta-xfce
│   └── README
├── meta-qt6
│   ├── classes
│   ├── coin
│   ├── conf
│   ├── COPYING.MIT
│   ├── licenses
│   ├── README.md
│   ├── recipes-core
│   ├── recipes-devtools
│   └── recipes-qt
├── meta-raspberrypi
│   ├── classes
│   ├── conf
│   ├── COPYING.MIT
│   ├── docs
│   ├── dynamic-layers
│   ├── files
│   ├── kas-poky-rpi.yml
│   ├── lib
│   ├── README.md
│   ├── recipes-bsp
│   ├── recipes-connectivity
│   ├── recipes-core
│   ├── recipes-devtools
│   ├── recipes-graphics
│   ├── recipes-kernel
│   ├── recipes-multimedia
│   └── wic
├── meta-swupdate
│   ├── classes
│   ├── conf
│   ├── COPYING.MIT
│   ├── README
│   ├── recipes-core
│   ├── recipes-devtools
│   ├── recipes-extended
│   ├── recipes-lua
│   └── recipes-support
├── poky
│   ├── bitbake
│   ├── build-microchip-backup
│   ├── contrib
│   ├── documentation
│   ├── LICENSE
│   ├── LICENSE.GPL-2.0-only
│   ├── LICENSE.MIT
│   ├── MEMORIAM
│   ├── meta
│   ├── meta-poky
│   ├── meta-selftest
│   ├── meta-skeleton
│   ├── meta-yocto-bsp
│   ├── oe-init-build-env
│   ├── pn-buildlist
│   ├── README.hardware -> meta-yocto-bsp/README.hardware
│   ├── README.OE-Core
│   ├── README.poky -> meta-poky/README.poky
│   ├── README.qemu
│   ├── rpi-build
│   ├── scripts
│   └── task-depends.dot
├── rpi-build
│   ├── bitbake-cookerdaemon.log
│   ├── cache
│   ├── conf
│   ├── sstate-cache
│   └── tmp

```

[-- Attachment #2: Type: text/html, Size: 4892 bytes --]

Re: Correct build folder location

[Electronic Consult]

[-- Attachment #1: Type: text/plain, Size: 482 bytes --]

As an update for anyone looking at this..

I managed to get the raspberry pi build going. It seems after running

source oe-init-build-env rpi-build
the local.conf from meta-atmel was copied into the rpi-build folder. This local.conf amongst other things had

DISTRO ?= "poky-atmel"

Which was causing the issue.

However if anyone could point out best practice on folder location I'd be grateful. Build folders inside or outside the poky directory?

Regards,

Owen

[-- Attachment #2: Type: text/html, Size: 549 bytes --]

Re: [yocto] Correct build folder location

[Luca Ceresoli]

Hello,

On Thu, 13 Apr 2023 12:52:28 -0700
"Electronic Consult" <electronicconsult1@gmail.com> wrote:

> As an update for anyone looking at this..
> 
> I managed to get the raspberry pi build going. It seems after running
> 
> source oe-init-build-env rpi-build
> the local.conf from meta-atmel was copied into the rpi-build folder.

The selection of the sample local.conf depends on the TEMPLATECONF
variable. You likely followed the meta-atmel instructions
(https://github.com/linux4sam/meta-atmel/blob/kirkstone/README) which,
at step 6, ask you to set TEMPLATECONF to point to the meta-atmel
sample files.

Just skip step 6.

Best regards,
Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com