From: Eli Zaretskii <eliz@gnu.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: alexott@gmail.com, eric@siege-engine.com, emacs-devel@gnu.org
Subject: Re: CEDET calls cpp -E -dM -x c++ /dev/null
Date: Thu, 02 Jul 2009 06:24:00 +0300 [thread overview]
Message-ID: <83tz1v3gz3.fsf@gnu.org> (raw)
In-Reply-To: <e01d8a50907011325u665307acma92a6df1664b67b2@mail.gmail.com>
> Date: Wed, 1 Jul 2009 22:25:32 +0200
> From: Lennart Borgman <lennart.borgman@gmail.com>
> Cc: emacs-devel@gnu.org, alexott@gmail.com, eric@siege-engine.com
>
> I see another problem in semantic-gcc-setup. It tries to guess the
> include paths and does this
>
> (let* ((try-paths (list "/usr/include" (concat prefix "/include")
> (concat prefix "/include/c++/" ver)
> (concat prefix "/include/c++/" ver "/" host )
> )))
>
> Can't gcc or cpp give some better information about include paths that
> semantic can use? Where is this information?
I thought one of the -print-* options could show the place of the
headers, but I cannot get them to do this. This is the closest:
D:\usr\eli\data>cpp -print-file-name=libmingwex.a
D:/usr/bin/../lib/gcc/mingw32/3.4.2/../../../libmingwex.a
I guess the place where the headers live should be customizable
instead of being hardcoded.
next prev parent reply other threads:[~2009-07-02 3:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 19:06 CEDET calls cpp -E -dM -x c++ /dev/null Lennart Borgman
2009-07-01 19:20 ` Eli Zaretskii
2009-07-01 19:25 ` Lennart Borgman
2009-07-01 19:36 ` Eli Zaretskii
2009-07-01 20:01 ` Sean O'Rourke
2009-07-01 20:16 ` Lennart Borgman
2009-07-01 20:32 ` Sean O'Rourke
2009-07-01 20:25 ` Lennart Borgman
2009-07-02 3:24 ` Eli Zaretskii [this message]
2009-07-02 3:34 ` Eric M. Ludlam
2009-07-02 18:13 ` Lennart Borgman
2009-07-02 19:29 ` Eli Zaretskii
2009-07-03 0:31 ` Lennart Borgman
2009-07-03 0:46 ` Miles Bader
2009-07-03 1:13 ` Lennart Borgman
2009-07-03 9:36 ` Eli Zaretskii
2009-07-03 11:22 ` Lennart Borgman
2009-07-01 19:58 ` Lennart Borgman
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=83tz1v3gz3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=alexott@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
--cc=lennart.borgman@gmail.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.
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).