From: Josh Varner <jlvarner@gmail.com>
Cc: nickrob@snap.net.nz, jan.h.d@swipnet.se, rms@gnu.org,
emacs-devel@gnu.org
Subject: Re: /lib/cpp not found in c-mode
Date: Wed, 4 May 2005 14:04:40 -0500 [thread overview]
Message-ID: <92a5eb4705050412045d89ddbe@mail.gmail.com> (raw)
In-Reply-To: <jwvekcoxjm1.fsf-monnier+emacs@gnu.org>
On 5/3/05, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > Don't know about others, but the reason why I don't use c-macro-expand
> > is because it basically can't work right without parsing my
> > Makefile(s) to know which include dirs should be used. And since it
> > doesn't do that, I've found it of little use.
>
> > What information would it need in order to DTRT for you?
>
. . .
> Of course I can also manually take the relevant info from the Makefile and
> put it into c-macro-cppflags, but doing that for each and every project
> I work on is just too much trouble for me to even try it.
>
Assuming you do your compiles from emacs you should have the full
command lines used to compile the sources, i.e. containing all of the
relevant -I and -D's. Could a function be used to grab this
information out of the compilation buffers and store it for use by
c-macro-expand?
If this was automated in such a way that you could have an association
between files, or groups of files and the options used by
c-macro-expand, a hook in the compilation buffer could grab that
information during each build for later use. That would give you the
flexibility without the tedium.
Josh
next prev parent reply other threads:[~2005-05-04 19:04 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 16:47 /lib/cpp not found in c-mode Stefan Monnier
2005-05-01 20:23 ` Eli Zaretskii
2005-05-02 1:29 ` Nick Roberts
2005-05-02 15:44 ` Stefan Monnier
2005-05-02 21:30 ` Nick Roberts
2005-05-04 9:46 ` Nick Roberts
2005-05-01 23:40 ` Nick Roberts
2005-05-02 4:14 ` Jan D.
2005-05-02 6:46 ` Nick Roberts
2005-05-02 19:58 ` Jan D.
2005-05-02 21:15 ` Nick Roberts
2005-05-02 22:16 ` Stefan Monnier
2005-05-03 4:05 ` Nick Roberts
2005-05-03 15:45 ` Stefan Monnier
2005-05-03 21:36 ` Nick Roberts
2005-05-03 17:12 ` Richard Stallman
2005-05-03 18:18 ` Stefan Monnier
[not found] ` <20050503233249.1C2799F4ED@mirror.positive-internet.com>
2005-05-03 23:45 ` Stefan Monnier
2005-05-04 22:05 ` Richard Stallman
2005-05-04 19:04 ` Josh Varner [this message]
2005-05-03 19:13 ` Eli Zaretskii
2005-05-03 20:23 ` Stefan Monnier
2005-05-04 20:58 ` Eli Zaretskii
2005-05-05 10:58 ` Nick Roberts
2005-05-05 17:43 ` Eli Zaretskii
[not found] ` <0FA9201A-8390-4924-BDE3-2857B0A33576@swipnet.se>
2005-05-05 21:54 ` Nick Roberts
2005-05-06 4:51 ` Jan D.
2005-05-06 7:43 ` Eli Zaretskii
2005-05-03 4:14 ` Jan D.
2005-05-03 19:49 ` Magnus Henoch
2005-05-04 20:49 ` Nick Roberts
2005-05-05 14:17 ` Stefan Monnier
2005-05-05 17:50 ` Eli Zaretskii
2005-05-05 18:19 ` Stefan Monnier
2005-05-05 21:02 ` Nick Roberts
2005-05-06 12:34 ` Eli Zaretskii
2005-05-08 2:54 ` Nick Roberts
2005-05-08 4:28 ` Eli Zaretskii
2005-05-08 4:59 ` Nick Roberts
2005-05-08 16:12 ` Richard Stallman
2005-05-08 18:43 ` Eli Zaretskii
2005-05-08 16:12 ` Richard Stallman
2005-05-08 17:31 ` Stefan Monnier
2005-05-08 19:02 ` Eli Zaretskii
2005-05-08 19:41 ` Eli Zaretskii
2005-05-08 21:18 ` Stefan Monnier
2005-05-06 12:49 ` Eli Zaretskii
2005-05-06 22:41 ` Nick Roberts
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92a5eb4705050412045d89ddbe@mail.gmail.com \
--to=jlvarner@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=nickrob@snap.net.nz \
--cc=rms@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).