public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch] BaseTools: Add some posixlike files for Linux
Date: Mon, 26 Sep 2016 02:00:11 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14B47CC49@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1474771773-10832-1-git-send-email-yonghong.zhu@intel.com>

Yonghong:
  I apply this patch and run them in Linux. They doesn't work. Could you help try it?

Thanks
Liming
> -----Original Message-----
> From: Zhu, Yonghong
> Sent: Sunday, September 25, 2016 10:50 AM
> To: edk2-devel@lists.01.org
> Cc: Gao, Liming <liming.gao@intel.com>
> Subject: [Patch] BaseTools: Add some posixlike files for Linux
> 
> Add the posixlike files for Rsa2048Sha256Sign, Rsa2048Sha256GenerateKeys
> and Pkcs7Sign.
> 
> Cc: Liming Gao <liming.gao@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
> ---
>  BaseTools/BinWrappers/PosixLike/Pkcs7Sign                 | 14 ++++++++++++++
>  BaseTools/BinWrappers/PosixLike/Rsa2048Sha256GenerateKeys | 14
> ++++++++++++++
>  BaseTools/BinWrappers/PosixLike/Rsa2048Sha256Sign         | 14
> ++++++++++++++
>  3 files changed, 42 insertions(+)
>  create mode 100755 BaseTools/BinWrappers/PosixLike/Pkcs7Sign
>  create mode 100755
> BaseTools/BinWrappers/PosixLike/Rsa2048Sha256GenerateKeys
>  create mode 100755 BaseTools/BinWrappers/PosixLike/Rsa2048Sha256Sign
> 
> diff --git a/BaseTools/BinWrappers/PosixLike/Pkcs7Sign
> b/BaseTools/BinWrappers/PosixLike/Pkcs7Sign
> new file mode 100755
> index 0000000..214d88f
> --- /dev/null
> +++ b/BaseTools/BinWrappers/PosixLike/Pkcs7Sign
> @@ -0,0 +1,14 @@
> +#!/usr/bin/env bash
> +#python `dirname $0`/RunToolFromSource.py `basename $0` $*
> +
> +# If a python2 command is available, use it in preference to python
> +if command -v python2 >/dev/null 2>&1; then
> +    python_exe=python2
> +fi
> +
> +full_cmd=${BASH_SOURCE:-$0} # see
> http://mywiki.wooledge.org/BashFAQ/028 for a discussion of why $0 is not a
> good choice here
> +dir=$(dirname "$full_cmd")
> +cmd=${full_cmd##*/}
> +
> +export PYTHONPATH="$dir/../../Source/Python"
> +exec "${python_exe:-python}" "$dir/../../Source/Python/$cmd/$cmd.py"
> "$@"
> diff --git a/BaseTools/BinWrappers/PosixLike/Rsa2048Sha256GenerateKeys
> b/BaseTools/BinWrappers/PosixLike/Rsa2048Sha256GenerateKeys
> new file mode 100755
> index 0000000..2cddde9
> --- /dev/null
> +++ b/BaseTools/BinWrappers/PosixLike/Rsa2048Sha256GenerateKeys
> @@ -0,0 +1,14 @@
> +#!/usr/bin/env bash
> +#python `dirname $0`/RunToolFromSource.py `basename $0` $*
> +
> +# If a python2 command is available, use it in preference to python
> +if command -v python2 >/dev/null 2>&1; then
> +    python_exe=python2
> +fi
> +
> +full_cmd=${BASH_SOURCE:-$0} # see
> http://mywiki.wooledge.org/BashFAQ/028 for a discussion of why $0 is not a
> good choice here
> +dir=$(dirname "$full_cmd")
> +cmd=${full_cmd##*/}
> +
> +export PYTHONPATH="$dir/../../Source/Python"
> +exec "${python_exe:-python}"
> "$dir/../../Source/Python/Rsa2048Sha256Sign/$cmd.py" "$@"
> diff --git a/BaseTools/BinWrappers/PosixLike/Rsa2048Sha256Sign
> b/BaseTools/BinWrappers/PosixLike/Rsa2048Sha256Sign
> new file mode 100755
> index 0000000..214d88f
> --- /dev/null
> +++ b/BaseTools/BinWrappers/PosixLike/Rsa2048Sha256Sign
> @@ -0,0 +1,14 @@
> +#!/usr/bin/env bash
> +#python `dirname $0`/RunToolFromSource.py `basename $0` $*
> +
> +# If a python2 command is available, use it in preference to python
> +if command -v python2 >/dev/null 2>&1; then
> +    python_exe=python2
> +fi
> +
> +full_cmd=${BASH_SOURCE:-$0} # see
> http://mywiki.wooledge.org/BashFAQ/028 for a discussion of why $0 is not a
> good choice here
> +dir=$(dirname "$full_cmd")
> +cmd=${full_cmd##*/}
> +
> +export PYTHONPATH="$dir/../../Source/Python"
> +exec "${python_exe:-python}" "$dir/../../Source/Python/$cmd/$cmd.py"
> "$@"
> --
> 2.6.1.windows.1



  reply	other threads:[~2016-09-26  2:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-25  2:49 [Patch] BaseTools: Add some posixlike files for Linux Yonghong Zhu
2016-09-26  2:00 ` Gao, Liming [this message]
2016-09-27  5:36   ` Gao, Liming
2016-09-27  5:40     ` Zhu, Yonghong

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-list 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=4A89E2EF3DFEDB4C8BFDE51014F606A14B47CC49@shsmsx102.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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