public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <rebecca@bsdio.com>,
	"'Chao Li'" <lichao@loongson.cn>,
	"'Baoqi Zhang'" <zhangbaoqi@loongson.cn>,
	"'Dongyan Qian'" <qiandongyan@loongson.cn>
Cc: "'Michael D Kinney'" <michael.d.kinney@intel.com>
Subject: 回复: [edk2-devel] Reducing the size of the loongarch64 toolchain download
Date: Fri, 30 Dec 2022 10:11:20 +0800	[thread overview]
Message-ID: <01a501d91bf4$025d7630$07186290$@byosoft.com.cn> (raw)
In-Reply-To: <5f88e31c-444e-f7c4-668e-c1221d012f40@bsdio.com>

Rebecca:
 BaseTools/Bin/gcc_loongarch64_unknown_linux_extdep directory should be created after Stuart build. Please confirm it. 

Thanks
Liming
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Rebecca Cran
> 发送时间: 2022年12月28日 16:15
> 收件人: Chao Li <lichao@loongson.cn>; Baoqi Zhang
> <zhangbaoqi@loongson.cn>; Dongyan Qian <qiandongyan@loongson.cn>
> 抄送: devel@edk2.groups.io; Michael D Kinney <michael.d.kinney@intel.com>
> 主题: [edk2-devel] Reducing the size of the loongarch64 toolchain download
> 
> I noticed the BaseTools/Bin/gcc_loongarch64_unknown_linux_extdep
> directory is 3.2GB. However, 2.6GB of that is from target/usr/lib64
> (which includes X and Qt libraries).
> 
> Since it appears the gcc binaries are statically linked, I was wondering
> if the lib and lib64 directories could be excluded from future uploads?
> 
> 
> --
> Rebecca Cran
> 
> 
> 
> 
> 




  parent reply	other threads:[~2022-12-30  2:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28  8:15 Reducing the size of the loongarch64 toolchain download Rebecca Cran
2022-12-28  8:55 ` 回复:Reducing " Chao Li
2022-12-30  2:11 ` gaoliming [this message]
2022-12-30  3:24   ` 回复: [edk2-devel] Reducing " Rebecca Cran

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='01a501d91bf4$025d7630$07186290$@byosoft.com.cn' \
    --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