Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: where to put headers in new port
Date: Wed, 15 Jan 2003 16:35:00 -0000	[thread overview]
Message-ID: <013a01c2bcb4$0c339f00$0202040a@catdog> (raw)
In-Reply-To: <3E2588FB.4070209@redhat.com>

> > We have several header files that are included with our QNX port of gdb
> > relating to registers, remote protocols, etc.
> >
> > When we were maintaining our own port, we just put them in the top-level
> > include directory but now that we are trying to submit our port to your
cvs,
> > that seems less than appropriate.
> >
> > My first thought was just to create a qnxnto subdirectory under the
include
> > directory but I thought I should ask if anyone has any better
suggestions
> > first.
>
> It really depends on what the files contain.  sim/gdb register number
> tables appear in include/gdb/CPU-sim.h, for instance.
>
> What is nto?

nto is just a short form for Neutrino as in "The QNX Neutrino Operating
System".  Previously there was QNX2 and QNX4.   QNX6 runs the Neutrino
microkernel which is distinct from the kernels run by earlier incarnations.
Can you tell that all our naming, etc. is done by marketing people?  It gets
more confusing than that (QNX Momentics Development Suite for the Neutrino
OS hosted on Solaris, Windows, Linux and Neutrino ;-) but we use 'nto' in
much the same way as 'linux' or 'nbsd': a simple short form for a particular
OS.  I favour using nto instead of qnx purely as a way of future-proofing
against a new kernel if there ever was one.  In this case, QNX is the
company, nto is the OS.

cheers,

Kris


  reply	other threads:[~2003-01-15 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 15:46 Kris Warkentin
2003-01-15 16:15 ` Andrew Cagney
2003-01-15 16:35   ` Kris Warkentin [this message]
2003-01-15 19:37   ` Kris Warkentin

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='013a01c2bcb4$0c339f00$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.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