public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrew Fish" <afish@apple.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>, prabin.ca@arm.com
Subject: Re: [edk2-devel] Overriding of linker in ed2 build system
Date: Wed, 21 Oct 2020 08:39:50 -0700	[thread overview]
Message-ID: <78AA7491-0AAF-4452-8B49-C1E2DD7D2274@apple.com> (raw)
In-Reply-To: <25627.1603291168254535564@groups.io>

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

Prabin,

Conf/tools_def.txt is the local untracked by git copy of the file that the build actually uses. The Conf/tools_def.txt does NOT get overwritten by the BaseTools/Conf/tools_def.template if it exists. So you can edit Conf/tools_def.txt  locally for an experiment. If you change  BaseTools/Conf/tools_def.template then people need to force the update via `. edksetup.sh —reconfig`, if they have a local copy. 

Thanks,

Andrew Fish

> On Oct 21, 2020, at 7:39 AM, Prabin CA <prabin.ca@arm.com> wrote:
> 
> Hi Andrew,
> 
> Yes, it copy from  BaseTools/Conf/tools_def.template to Conf/tools_def.txt, so if we make any changes in Conf/tools_def.txt will be over write by BaseTools/Conf/tools_def.template, then why we have to edit txt file instead template. Please confirm we have to edit template file or txt file. and we are made changes such as setting target and appending LDFLAGS on template file.
> 


[-- Attachment #2: Type: text/html, Size: 1538 bytes --]

  reply	other threads:[~2020-10-21 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20 18:44 Overriding of linker in ed2 build system Prabin CA
2020-10-21 14:05 ` [edk2-devel] " Andrew Fish
2020-10-21 14:39   ` Prabin CA
2020-10-21 15:39     ` Andrew Fish [this message]
2020-10-28  9:35       ` Prabin CA
2020-10-30  2:04         ` 回复: " gaoliming

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=78AA7491-0AAF-4452-8B49-C1E2DD7D2274@apple.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