public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ben Elliston <bje@redhat.com>
To: Nacho de los Ríos Tormo <irios@proin.es>
Cc: <sourcenav@sources.redhat.com>
Subject: Re:include file problems
Date: Tue, 28 Nov 2000 13:42:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.30.0011290839560.17839-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <00112818511300.00635@irios>

   SNav only manages to find the correct files if I include them
   explicitly in the project (which calls for a trip to the project
   editor and to have the project reparsed). But these files themselves
   do include a variety of other files, which in their turn call others.

I could be wrong, but my recollection is that S-N will only include files in
your project that are explicitly listed at project creation time.  That is,
#include directives are not followed as you might expect.  This is in fact a
good idea, since it gives you more control over how big your database gets.

Often, users don't care about header files or, say, the function prototype
for strcmp(3).  If you use the project editor to include all of
/usr/include, does it work as expected?

Ben

  parent reply	other threads:[~2000-11-28 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-28  9:52 Nacho de los Ríos Tormo
2000-11-28 10:14 ` Mo DeJong
2000-11-29  2:41   ` Nacho de los Ríos Tormo
2000-11-29  4:02     ` Nacho de los Ríos Tormo
2000-11-29  4:10       ` include " Bruce Stephens
2000-11-28 13:42 ` Ben Elliston [this message]
     [not found] <Pine.LNX.4.30.0011292313170.20902-100000@moshpit.cygnus.com>
2000-11-29  6:53 ` Nacho de los Ríos Tormo

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=Pine.LNX.4.30.0011290839560.17839-100000@moshpit.cygnus.com \
    --to=bje@redhat.com \
    --cc=irios@proin.es \
    --cc=sourcenav@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).