From: cajus.hahn@de.abb.com
To: sourcenav@sources.redhat.com
Subject: Relative path names
Date: Thu, 19 Jul 2001 05:08:00 -0000 [thread overview]
Message-ID: <OF11518CAA.927D4057-ONC1256A8E.004132C7@de.abb.com> (raw)
This is another try to get help with the relative path names problem that
was posted 13 May 2001 by Charles.
He asked:
"I noticed to specifiy include paths, libraries, etc, Source Nagivator automot
expands it to an abosulte path name.
Anyway to make it save them as relative to the project directory, so one can
effectively share project files between people?"
I have the same problem.
In addition I would like to use shell variables in the path name
i.e. $home/$user/myproject
where $home and $user are exported shell variables set by the profile file.
Is there any way to enter relative paths or shell variables ?
Some paths can only be choosen from a file chooser box where no input line exists!
Cajus
next reply other threads:[~2001-07-19 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 5:08 cajus.hahn [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-13 6:43 punt
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=OF11518CAA.927D4057-ONC1256A8E.004132C7@de.abb.com \
--to=cajus.hahn@de.abb.com \
--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).