@robimarko:
Regarding 6d45544 and 8e272a6. How is it meant to be done to build such an image that is marked DEFAULT:=n? I want to build (via imagebuilder) tplink_tl-wr1043nd-v1 that doesn't work anymore since 24.10.2. I had to patch .targetinfo and generic-tp-link.mk to DEFAULT:=y to make it work again. Edit: Delete .profiles.mk as well so it can be regenerated.
Is this the correct procedure?
Edit: Errors/Keywords:
Profile "tplink_tl-wr1043nd-v1" does not exist!
Use "make info" to get a list of available profile names.
make[1]: *** [Makefile:303: _check_profile] Error 1
make: *** [Makefile:335: image] Error 2
JSON info file script could not find any JSON files for target
Devices with DEFAULT=n are now explicitly removed from the imagebuilders so as to not break any downstream use of them (specifically the docker imagebuilder containers during the smoke tests).
If your patches work for you, that sounds like you're on the right track. I'm not sure why that device is marked to be ignored, but if you can figure out the root cause for DEFAULT=n and fix it, maybe put in a PR to return it to the builds? (I think sometimes it's improper/proprietary licensing of binary blobs from the manufacturer, so it's not possible for the project to build, but maybe an individual can.)