From: Luis Machado <lgustavo@codesourcery.com>
To: Yue Lu <hacklu.newborn@gmail.com>
Cc: gdb@sourceware.org, Thomas Schwinge <thomas@codesourcery.com>
Subject: Re: How to share code between [gdb]/gnu-nat.c with [gdb]/gdbserver/gnu-hurd-low.c?
Date: Mon, 12 Aug 2013 12:25:00 -0000 [thread overview]
Message-ID: <5208D432.1010307@codesourcery.com> (raw)
In-Reply-To: <CAB8fV=jzv_rPHP3-HQVBA-pCNZNat6PNbh+OJEU7tZgQdKX3+w@mail.gmail.com>
On 08/12/2013 05:36 AM, Yue Lu wrote:
> Hi all,
>
> When I working with porting gdbserver to GNU/Hurd I found I alway need
> to duplicate code from [gdb]/gnu-nat.c to my new file
> [gdb]/gdb/server/gnu-hurd.low.c. There are too many functions and
> structures can be shared between the two file only need a little
> change or even without any change.
>
> I don't have good ideal to share the code, can you give me any
> suggestions? Thank you.
Any common code you come up with can potentially be included inside
gdb/common. Then you need to make sure both gdb's and gdbserver's
Makefile's are adjusted to match that.
The more you can share, the better. It helps keep things organized that way.
There is an ongoing discussion related to proper naming of files and
paths, but that should not stop you from sharing code anyway.
Luis
prev parent reply other threads:[~2013-08-12 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 8:36 Yue Lu
2013-08-12 12:25 ` Luis Machado [this message]
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=5208D432.1010307@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=hacklu.newborn@gmail.com \
--cc=thomas@codesourcery.com \
/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