barebox: also use image suffix for barebox-flash-image and EFI

[rohieb]

This makes it possible to have multiple barebox packages in a BSP without them overwriting each other's image in the deploy stage, even when they're building an EFI image or only a barebox-flash-image.

[ejoerns]

About this, I am not sure whether a suffix is the right choice here or if we should simply allow setting the resulting artifact name.

Naming the EFI binary barebox.efi.something also sounds inconvenient for me. Something like `barebox-${MACHINE}.efi" would be more appropriate I guess.

It might be also worth looking into u-boot.inc and copy some approaches from there.
This allows setting UBOOT_ELF to the expected u-boot binary name and installs this into ${DEPLOYDIR}/u-boot-${type}-${PV}-${PR}.${UBOOT_ELF_SUFFIX}. We could probably also use a similar approach to bypass the default deploy handling and instead of deploying everything that was built with barebox, deploy only ${BAREBOX_ELF} to a configurable destination. This would be applicable to more than just barebox.efi.

Further suggestions very welcome..

Also, an added variable should have a bit of documentation in the class, at least with a VARNAME[doc] = "description" entry and probably a weak default to an empty string?

[ejoerns]

Any further news/ideas here?

[a3f]

I have since learnt that barebox for close to 7 years now has been generating a barebox-flash-images file with a list of generated images.

[a3f]

I have since learnt that barebox for close to 7 years now has been generating a barebox-flash-images file with a list of generated images.

This is now used in PTXdist:

	@$(foreach image, $(shell cat $(BAREBOX_BUILD_DIR)/barebox-flash-images), \
		$(call ptx/image-install, BAREBOX, $(BAREBOX_BUILD_DIR)/$(image))$(ptx/nl) \
		if [ ! -e $(IMAGEDIR)/barebox-image ]; then \
			$(call ptx/image-install-link, BAREBOX, $(notdir $(image)), barebox-image); \
		fi$(ptx/nl))