public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Juhana Sadeharju <kouhia@nic.funet.fi>
To: sourcenav@sources.redhat.com
Subject: Command line use?
Date: Mon, 10 Sep 2001 09:44:00 -0000	[thread overview]
Message-ID: <20010910164341Z42906-432+2185@nic.funet.fi> (raw)

Hello. If I browsed User Guide correctly, SN cannot be operated
from command line. Following simple tasks should go through command
line; please consider.

I looked for a software for creating Makefiles automatically because
I have an old software having hundrets of files in nearly 200 directories.
Instead of modifying 200 Makefiles or Makefiles.am, it would make
sense if a software (SN?) generates the Makefiles.

For the task, I don't need to maintain any files -- simple making of
the makefiles would do fine. If anything is missing (from system files),
then error reports are okay. So, simple "snavigator justdoit" command
line command would do fine for me. "make all" should compile all
executables, one per main() found, and build a library file based
on (given?) .h files.

My own library of routines has several tens of .c/.h files. When I
write source for a new executable, I just add dependencies to Makefile
and not pack my library to a lib file. Here I would need a command
"snavigator justdoit" which creates makefiles so that "make main"
would compile main() in file main.c and "make another" would compile
the main() in file another.c.

Library could similarly be made by "snavigator justdoit libhere.h libhere".
"make libhere" would actually compile and assemble the "libhere" library
file.

I don't need and don't want understand the Makefile system beyond this.
So, is Source-Navigator for me, or should I look for a better program?
(Or can SN be made simple for the simple tasks like above?)

Best Regards,

Juhana

PS. I'm not in the mailing list, but I read replies from the archive

             reply	other threads:[~2001-09-10  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10  9:44 Juhana Sadeharju [this message]
2001-09-11  0:43 ` Debugging SN source jithendra nath
2001-09-12 12:26   ` Ian Roxborough

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=20010910164341Z42906-432+2185@nic.funet.fi \
    --to=kouhia@nic.funet.fi \
    --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).