Paul Spooren [2020-03-03 17:02:07]:
> On 02.03.20 23:12, Petr Štetiar wrote:
> > Paul Spooren [2020-03-02 16:19:05]:
> >
> > > - .IGNORE: $(BIN_DIR)/$(call IMAGE_NAME,$(1),$(2))
> > >
> > > [...]
> > >
> > > $(BIN_DIR)/$(call IMAGE_NAME,$(1),$(2)): $(KDIR)/tmp/$(call
> > > IMAGE_NAME,$(1
Hi Petr,
On 02.03.20 23:12, Petr Štetiar wrote:
Paul Spooren [2020-03-02 16:19:05]:
- .IGNORE: $(BIN_DIR)/$(call IMAGE_NAME,$(1),$(2))
[...]
$(BIN_DIR)/$(call IMAGE_NAME,$(1),$(2)): $(KDIR)/tmp/$(call
IMAGE_NAME,$(1),$(2))
- cp $$^ $$@
+ -cp $$^ $$@
The prefixed dash ignor
Paul Spooren [2020-03-02 16:19:05]:
> - .IGNORE: $(BIN_DIR)/$(call IMAGE_NAME,$(1),$(2))
>
> [...]
>
> $(BIN_DIR)/$(call IMAGE_NAME,$(1),$(2)): $(KDIR)/tmp/$(call
> IMAGE_NAME,$(1),$(2))
> - cp $$^ $$@
> + -cp $$^ $$@
>
> The prefixed dash ignores a failure.
This change seems
This problem occurs also fox x86, the problem is that the image function is
not properly called. Maybe because IMX6 only offer a default target but no
profiles, resulting in an empty profiles.json file - I think. I started
(based on Lynxis draft) reworking the x86 so it creates also JSON files[0
Paul Spooren [2020-03-01 14:10:16]:
> On 01.03.20 02:34, Petr Štetiar wrote:
> > Paul Spooren [2020-02-29 16:48:50]:
> >
> > FYI:
> >
> > $ grep JSON .config
> > CONFIG_JSON_OVERVIEW_IMAGE_INFO=y
> >
> > $ cat bin/targets/imx6/generic/profiles.json
> > {}
>
> This problem occurs also
On 01.03.20 02:34, Petr Štetiar wrote:
Paul Spooren [2020-02-29 16:48:50]:
FYI:
$ grep JSON .config
CONFIG_JSON_OVERVIEW_IMAGE_INFO=y
$ cat bin/targets/imx6/generic/profiles.json
{}
This problem occurs also fox x86, the problem is that the image function
is not properly called. Ma
On 01.03.20 02:29, Moritz Warning wrote:
Hi Paul,
as I see it, there are now two JSON options:
- creates the single JSON files in the $(KDIR)/tmp folder
- create a per target overview JSON that contains nearly all data of the single
JSON files
This is the way I implemented it now :)
Questi
Paul Spooren [2020-02-29 16:48:50]:
FYI:
$ grep JSON .config
CONFIG_JSON_OVERVIEW_IMAGE_INFO=y
$ cat bin/targets/imx6/generic/profiles.json
{}
> diff --git a/config/Config-build.in b/config/Config-build.in
> index 6a6fb2882c..57428399ab 100644
> --- a/config/Config-build.in
> +++ b/config
Hi Paul,
as I see it, there are now two JSON options:
- creates the single JSON files in the $(KDIR)/tmp folder
- create a per target overview JSON that contains nearly all data of the single
JSON files
Questions:
- Why not only have one JSON menu option that create the one per target JSON
fi
JSON info files contain machine readable information of built profiles
and resulting images. These files where added via 881ed09ee6e2. They are
useful for firmware wizards and script checking for reproducibility.
Currently all JSON files are stored next to the built images, resulting
in up to 168
10 matches
Mail list logo
