Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Enze Li via Gdb-patches <gdb-patches@sourceware.org>
To: Andreas Schwab <schwab@linux-m68k.org>,
	Enze Li via Gdb-patches <gdb-patches@sourceware.org>
Cc: brobecker@adacore.com
Subject: Re: [PATCH v2] gdb: AC_INIT should be called with package and version arguments
Date: Fri, 26 Nov 2021 00:20:28 +0800	[thread overview]
Message-ID: <MEAP282MB029319E026FD383F1669FBF7DD629@MEAP282MB0293.AUSP282.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87czmqgbdo.fsf@igel.home>

Hi Andreas,

Thanks for the review.

I thought I'd do some explaining.

The version info that will be generated by this patch and the version
info generated in gdb/version.c are both from the version.in file. The
difference is that the patch is generated before compilation, while the
version info generated in the version.c file is generated during the
compilation process. Note that the version.c file is dynamically
generated by the create-version.sh script.

This is my understanding. I'm not sure I've articulated that clearly.

If there is a demand, I think we can modify it a bit more, we can use
the macros in the config.h header file automatically generated by this
patch and embed them directly into the c code.

It's just a thought.

If I'm going in the wrong direction, please feel free to point it out.
I would be happy to ask for your advice.

Thanks,
Enze

On Tue, 2021-11-23 at 16:06 +0100, Andreas Schwab wrote:
> 
> That should produce the same version as written in gdb/version.c.
> 
> Andreas.
> 


  reply	other threads:[~2021-11-25 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 14:16 Enze Li via Gdb-patches
2021-11-23 15:06 ` Andreas Schwab
2021-11-25 16:20   ` Enze Li via Gdb-patches [this message]
2021-11-25 17:30     ` Andreas Schwab

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=MEAP282MB029319E026FD383F1669FBF7DD629@MEAP282MB0293.AUSP282.PROD.OUTLOOK.COM \
    --to=gdb-patches@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=lienze2010@hotmail.com \
    --cc=schwab@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox