public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "PAUL KOVITZ" <pkovitz@home.com>
To: <sourcenav@sourceware.cygnus.com>
Subject: Problem with sources in multiple directories
Date: Fri, 23 Feb 2001 22:46:00 -0000	[thread overview]
Message-ID: <020e01c09e2d$e23ded00$0eb10918@potlnd1.or.home.com> (raw)

Hello. I am new to Source Navigator and I am having what must be a very
basic problem. I am running 4.52 Source Navigator on Windows 98 2nd edition
and the latest version of cygwin (I upgraded after I had this problem). I
have a project with sources in two separate directories as follows:
./src1/fn.h -- contains function headers for f1() and f2()
./src1/fn.c -- contains f1() and f2() definitions. includes fn.h
./src2/main.c -- contains main() definition. calls f1() includes fn.h
If I add only ./src1 to the build target, then I can compile fn.c (it won't
link because it doesn't have main).
If I add only ./src2 to the build target, then I can compile main.c (it
won't link because it doesn't have the functions in fn.c).
If I add both ./src1 and ./src2 to the build target, then fn.c does't
compile. The error message is:
make: *** No rule to make target `fn.h', needed by `fn.o'.  Stop.

I have changed the build rules so that both ./src1 and ./src2 are added
during gcc with the -I option. I thought this might be the VPATH problem I
was reading about in the archives, but upgrading my cygwin does not fix the
problem. What am I doing wrong? Any help would be greatly appreciated.
*********************************************
Paul Kovitz
*********************************************


             reply	other threads:[~2001-02-23 22:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-23 22:46 PAUL KOVITZ [this message]
2001-02-26 20:10 ` PAUL KOVITZ

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='020e01c09e2d$e23ded00$0eb10918@potlnd1.or.home.com' \
    --to=pkovitz@home.com \
    --cc=sourcenav@sourceware.cygnus.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).