[Buildroot] [PATCH 3/3] rpi-fw: New package

[Peter Korsgaard <jacmet@uclibc.org>]

>>>>> "Floris" == Floris Bos <bos@je-eigen-domein.nl> writes:

Hi,

 Floris> Fails to install.
 Floris> You need to create the target/boot directory first.

 Floris> ==

 Floris> /usr/bin/install -D -m 0644
 Floris> /hdd/max/dev/tmp/buildroot/output/build/rpi-fw-76d0ac38f16b6343c6155c80db1e4758b3a5838a/boot/bootcode.bin
 Floris> /hdd/max/dev/tmp/buildroot/output/target/boot/
 Floris> /usr/bin/install: target
 Floris> /hdd/max/dev/tmp/buildroot/output/target/boot/' is not a directory: No
 Floris> such file or directory
 Floris> make: ***
 Floris> [/hdd/max/dev/tmp/buildroot/output/build/rpi-fw-76d0ac38f16b6343c6155c80db1e4758b3a5838a/.stamp_target_installed]
 Floris> Error 1
 Floris> ==

That's the point of using install -D (create dest dirs as needed), but
you need to provide it with the destination file name as well - E.G
$(TARGET_DIR)/boot/bootcode.bin

 Floris> But another question would be if bootloader files really should be
 Floris> installed under target.
 Floris> Keep in mind that the Raspberry Pi boot files are normally kept on a
 Floris> FAT partition seperate from the root file system.

Indeed, it probably makes more sense to just put it in IMAGES_DIR
instead.

-- 
Bye, Peter Korsgaard