Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paulius Zaleckas <paulius.zaleckas@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] handling package souce in .zip file
Date: Mon, 29 Nov 2010 22:05:29 +0200	[thread overview]
Message-ID: <4CF40789.70905@gmail.com> (raw)
In-Reply-To: <1290814537.14151.55.camel@coalu.atr>

On 11/27/2010 01:35 AM, Lionel Landwerlin wrote:
> Le samedi 27 novembre 2010 ? 01:05 +0200, Paulius Zaleckas a ?crit :
>> On Fri, Nov 26, 2010 at 9:35 PM, Lionel Landwerlin
>> <llandwerlin@gmail.com>  wrote:
>>> What's about this :
>>>
>>> unzip file.zip /tmp/plop
>>> mv /tmp/plop/*/* output/build/myzippkg-0.1/
>>
>> Yes, this is almost what I was thinking, but the problem is that there
>> is no way to override "standard" buildroot extraction step or at least
>> I don't know it (using GENTARGET) :)
>>
>
> You just need to define a macro per ".ext", just like what we've got for
> the download macros.
>
> INFLATE.zip would be the 2 lines above, and for the rest it would be the
> "bzcat/zcat/cat | tar -C ...".

Yes, but the problem is here:

# Unpack the archive
$(BUILD_DIR)/%/.stamp_extracted:
	@$(call MESSAGE,"Extracting")
	$(Q)mkdir -p $(@D)
	$(Q)$(INFLATE$(suffix $($(PKG)_SOURCE))) $(DL_DIR)/$($(PKG)_SOURCE) | \
	$(TAR) $(TAR_STRIP_COMPONENTS)=1 -C $(@D) $(TAR_OPTIONS) -
# some packages have messed up permissions inside
	$(Q)chmod -R ug+rw $(@D)
	$(foreach hook,$($(PKG)_POST_EXTRACT_HOOKS),$(call $(hook))$(sep))
	$(Q)touch $@

As you can see $(INFLATE$(suffix $($(PKG)_SOURCE))) $(DL_DIR)/$($(PKG)_SOURCE)
output is piped to tar...

  reply	other threads:[~2010-11-29 20:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 18:37 [Buildroot] handling package souce in .zip file Paulius Zaleckas
2010-11-26 19:35 ` Lionel Landwerlin
2010-11-26 23:05   ` Paulius Zaleckas
2010-11-26 23:35     ` Lionel Landwerlin
2010-11-29 20:05       ` Paulius Zaleckas [this message]
2010-11-29 20:54         ` Thomas Petazzoni
2010-11-30 17:40         ` Lionel Landwerlin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CF40789.70905@gmail.com \
    --to=paulius.zaleckas@gmail.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox