From: Fangrui Song <i@maskray.me>
To: Rasmus Villemoes <rv@rasmusvillemoes.dk>
Cc: Nick Clifton <nickc@redhat.com>, binutils@sourceware.org
Subject: Re: [PATCH] allow empty string as argument to -Map
Date: Wed, 4 Nov 2020 16:47:02 -0800 [thread overview]
Message-ID: <20201105004702.4vrqyu4h2bx4ethh@gmail.com> (raw)
In-Reply-To: <4aecc1e8-40f7-7a6f-7072-62e1193726d2@rasmusvillemoes.dk>
On 2020-11-04, Rasmus Villemoes wrote:
>On 04/11/2020 12.07, Nick Clifton wrote:
>> Hi Rasmus,
>>
>>> Yes, exactly, please see my original use case: I'd like some way to get
>>> the build to produce map files for all the binaries/solibs etc.
>>> generated, without patching each individual project's build system and
>>> figuring out where to hook in.
>>
>> OK, so how about this:
>>
>> -Map=<file> Put the map into <file>. <file> can be relative or absolute.
>> -Map=<dir> Put the map into <dir>/basename (outfile).map. Overwrites existing maps.
This looks like a complex operation. Is it really needed?
>> -Map=% Put the map into (outfile).map. Includes all path components in (outfile)
Maybe -Map=%.map to avoid hard coding the extension name?
>> Would this work for you ?
>>
>
>Yes, absolutely. Thanks.
>
>Rasmus
next prev parent reply other threads:[~2020-11-05 0:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 7:01 Rasmus Villemoes
2020-05-27 16:50 ` Nick Clifton
2020-05-28 0:33 ` Rasmus Villemoes
2020-05-28 4:23 ` Fangrui Song
2020-05-28 9:54 ` Nick Clifton
2020-10-23 12:31 ` Rasmus Villemoes
2020-10-29 15:52 ` Nick Clifton
2020-10-30 12:37 ` Rasmus Villemoes
2020-10-30 16:35 ` Nick Clifton
2020-11-03 9:13 ` Rasmus Villemoes
2020-11-04 11:07 ` Nick Clifton
2020-11-04 11:13 ` Rasmus Villemoes
2020-11-05 0:47 ` Fangrui Song [this message]
2020-11-05 10:01 ` Nick Clifton
2020-11-05 11:41 ` Nick Clifton
2020-11-05 12:23 ` Rasmus Villemoes
2020-11-06 14:38 ` Nick Clifton
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=20201105004702.4vrqyu4h2bx4ethh@gmail.com \
--to=i@maskray.me \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=rv@rasmusvillemoes.dk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).