[meta-freescale] [3rdparty][PATCH] u-boot-boundary-fw-utils: Define a dummy fw_env.config

[Khem Raj]

When building the cross recipe it complains about missing file
especially on non arm/aarch64 targets

Fixes
WARNING:
/mnt/a/yoe/sources/meta-freescale-3rdparty/recipes-bsp/u-boot/u-boot-boundary-fw-utils_2018.07.bb:
Unable to get checksum for u-boot-boundary-fw-utils-cross SRC_URI entry
fw_env.config: file could not be found

Signed-off-by: Khem Raj <***@gmail.com>
---
recipes-bsp/u-boot/u-boot-boundary-fw-utils/fw_env.config | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 recipes-bsp/u-boot/u-boot-boundary-fw-utils/fw_env.config

diff --git a/recipes-bsp/u-boot/u-boot-boundary-fw-utils/fw_env.config b/recipes-bsp/u-boot/u-boot-boundary-fw-utils/fw_env.config
new file mode 100644
index 0000000..8af3596
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot-boundary-fw-utils/fw_env.config
@@ -0,0 +1,2 @@
+# This is a dummy file. If this is being used that means it is missing for the machine/arch
+# which is being compiled here

[Gary Bisson]

Hi,

Post by Khem Raj
When building the cross recipe it complains about missing file
especially on non arm/aarch64 targets
Fixes
Unable to get checksum for u-boot-boundary-fw-utils-cross SRC_URI entry
fw_env.config: file could not be found

We should then limit the package to ARM/ARM64 architectures only as it
should only be built for Boundary Devices platforms anyway (all of
which are ARM).

Adding a dummy config file doesn't feel right.

Also, this package should only be built when explicitly added to your
packages list, not sure why someone would build it when using machines
other than nitrogen*.

Regards,
Gary
--

[Khem Raj]

Post by Gary Bisson
Hi,

Post by Khem Raj
When building the cross recipe it complains about missing file
especially on non arm/aarch64 targets
Fixes
/mnt/a/yoe/sources/meta-freescale-3rdparty/recipes-bsp/u-boot/
Unable to get checksum for u-boot-boundary-fw-utils-cross SRC_URI entry
fw_env.config: file could not be found

We should then limit the package to ARM/ARM64 architectures only as it
should only be built for Boundary Devices platforms anyway (all of
which are ARM).
Adding a dummy config file doesn't feel right.
Also, this package should only be built when explicitly added to your
packages list, not sure why someone would build it when using machines
other than nitrogen*.

This all is true for target recipe and in a way we already cover that this
is a cross recipe type and I am not sure if we can apply target overrides
to it we can however make this dummy config apply conditionally for
class-cross kind recipe

Post by Gary Bisson
Regards,
Gary

[Otavio Salvador]

Post by Khem Raj
When building the cross recipe it complains about missing file
especially on non arm/aarch64 targets
Fixes
Unable to get checksum for u-boot-boundary-fw-utils-cross SRC_URI entry
fw_env.config: file could not be found

In cross case, we can still match the machine, can't we?

[Khem Raj]

On Mon, Oct 22, 2018 at 3:10 PM Otavio Salvador

Post by Otavio Salvador

Post by Khem Raj
When building the cross recipe it complains about missing file
especially on non arm/aarch64 targets
Fixes
Unable to get checksum for u-boot-boundary-fw-utils-cross SRC_URI entry
fw_env.config: file could not be found

In cross case, we can still match the machine, can't we?

arch I know, machine probably not. Need to check

Post by Otavio Salvador
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: [phone] Mobile: [phone]

--