All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Watt <jpewhacker@gmail.com>
To: changqing.li@windriver.com, yocto@yoctoproject.org
Subject: Re: [meta-mingw][PATCH V2] testsdk: enhance extract sdk part
Date: Mon, 21 Jan 2019 08:47:24 -0600	[thread overview]
Message-ID: <3f77d5c6f2d3be211c92b9fdfa3fa36ecf490aa1.camel@gmail.com> (raw)
In-Reply-To: <1547718545-238633-2-git-send-email-changqing.li@windriver.com>

Just FYI, I haven't forgot about this patch. I want to wait until the
dependent OE-core patch is at least in the master-next branch before I
apply this to the MinGW master-next branch. If you want to give me a
ping when the OE-core patch shows up in master-next, it would be very
helpful.

Thanks

On Thu, 2019-01-17 at 17:49 +0800, changqing.li@windriver.com wrote:
> From: Changqing Li <changqing.li@windriver.com>
> 
> Current sdk type is tar.xz, but for mingw sdk, since we
> have symlink under the sdk folder, 7zip which used to
> extract tar.xz cannot handle it, refer 7zip upstream bug:
> https://sourceforge.net/p/sevenzip/discussion/45797/thread/c71d6b96/
> so oe-core have add support of change SDK type to .zip, so correct
> the extract function.
> 
> Signed-off-by: Changqing Li <changqing.li@windriver.com>
> ---
>  lib/oeqa/sdkmingw/testsdk.py | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/oeqa/sdkmingw/testsdk.py
> b/lib/oeqa/sdkmingw/testsdk.py
> index 85fe3c6..173cfd9 100644
> --- a/lib/oeqa/sdkmingw/testsdk.py
> +++ b/lib/oeqa/sdkmingw/testsdk.py
> @@ -12,7 +12,7 @@ class TestSDKMinGW(TestSDK):
>          """
>          Get the name of the SDK file
>          """
> -        return
> d.expand("${SDK_DEPLOY}/${TOOLCHAIN_OUTPUTNAME}.tar.xz")
> +        return
> d.expand("${SDK_DEPLOY}/${TOOLCHAIN_OUTPUTNAME}.${SDK_ARCHIVE_TYPE}")
>  
>      def extract_sdk(self, tcname, sdk_dir, d):
>          """
> @@ -23,7 +23,14 @@ class TestSDKMinGW(TestSDK):
>          try:
>              # TODO: It would be nice to try and extract the SDK in
> Wine to make
>              # sure it is well formed
> -            subprocess.check_output(['tar', '-xf', tcname, '-C',
> sdk_dir])
> +            
> +            # TODO: Extract SDK according to SDK_ARCHIVE_TYPE, need
> to change if
> +            # oe-core support other types.
> +            if d.getVar("SDK_ARCHIVE_TYPE") == "zip":
> +                subprocess.check_output(['unzip', '-d', sdk_dir,
> tcname])
> +            else:
> +                subprocess.check_output(['tar', '-xf', tcname, '-C', 
> sdk_dir])
> +
>          except subprocess.CalledProcessError as e:
>              bb.fatal("Couldn't install the SDK:\n%s" %
> e.output.decode("utf-8"))
>  
> -- 
> 2.7.4
> 
-- 
Joshua Watt <JPEWhacker@gmail.com>



  reply	other threads:[~2019-01-21 14:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16  9:36 [meta-mingw][PATCH] mingw32-common: change mingw sdk to .zip type changqing.li
2019-01-16 13:12 ` Joshua Watt
2019-01-16 13:17   ` Burton, Ross
2019-01-17  7:49     ` Changqing Li
2019-01-17  9:49     ` [meta-mingw][PATCH V2] testsdk: enhance extract sdk part changqing.li
2019-01-17  9:49       ` changqing.li
2019-01-21 14:47         ` Joshua Watt [this message]
2019-01-22  1:28           ` Changqing Li
2019-05-05  7:05           ` Changqing Li

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=3f77d5c6f2d3be211c92b9fdfa3fa36ecf490aa1.camel@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=changqing.li@windriver.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.