From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15547 invoked by alias); 15 Jan 2003 16:35:22 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15538 invoked from network); 15 Jan 2003 16:35:21 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 209.249.29.67 with SMTP; 15 Jan 2003 16:35:21 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id LAA19058; Wed, 15 Jan 2003 11:26:33 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id LAA21725; Wed, 15 Jan 2003 11:35:09 -0500 Message-ID: <013a01c2bcb4$0c339f00$0202040a@catdog> From: "Kris Warkentin" To: "Andrew Cagney" Cc: References: <011601c2bcad$39347b20$0202040a@catdog> <3E2588FB.4070209@redhat.com> Subject: Re: where to put headers in new port Date: Wed, 15 Jan 2003 16:35:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2003-01/txt/msg00264.txt.bz2 > > 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