> Op 3 dec. 2018, om 23:20 heeft Daniel Engberg
> het volgende geschreven:
>
> On 2018-12-03 23:05, Paul Oranje wrote:
>>> Op 3 dec. 2018, om 10:57 heeft Daniel Engberg
>>> het volgende geschreven:
>>> Hi,
>>> Perhaps its worth considering adding bsdtar / libarchive
>>>
On 2018-12-03 23:05, Paul Oranje wrote:
Op 3 dec. 2018, om 10:57 heeft Daniel Engberg
het volgende geschreven:
Hi,
Perhaps its worth considering adding bsdtar / libarchive
(https://www.libarchive.org/) instead which handles various formats
including zip (via zlib) and is still active?
> Op 3 dec. 2018, om 10:57 heeft Daniel Engberg
> het volgende geschreven:
>
> Hi,
>
> Perhaps its worth considering adding bsdtar / libarchive
> (https://www.libarchive.org/) instead which handles various formats including
> zip (via zlib) and is still active? Another possible benefit would
Hi,
Perhaps its worth considering adding bsdtar / libarchive
(https://www.libarchive.org/) instead which handles various formats
including zip (via zlib) and is still active? Another possible benefit
would be that you would consolidate a few more tools into one.
Best regards,
Daniel
On 15/10/2018 23:24, Sven Roederer wrote:
Am Donnerstag, 11. Oktober 2018, 19:34:35 CEST schrieb Sven Roederer:
tools/firmware-utils/src/mksercommfw.c depends on the zip-tool to generate
the firmwareimage.
Thinking of this again, I wonder if it would be the proper way to build the
zip-tool as
Am Donnerstag, 11. Oktober 2018, 19:34:35 CEST schrieb Sven Roederer:
> tools/firmware-utils/src/mksercommfw.c depends on the zip-tool to generate
> the firmwareimage.
Thinking of this again, I wonder if it would be the proper way to build the
zip-tool as y host-command like we do for tar and
