From: Dan Mick <dan.mick@inktank.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: include/ and -I
Date: Fri, 02 Nov 2012 16:35:20 -0700 [thread overview]
Message-ID: <509458B8.8070709@inktank.com> (raw)
In-Reply-To: <509437D1.9080105@inktank.com>
On 11/02/2012 02:14 PM, Dan Mick wrote:
> I was somewhat surprised to note that we don't build with -I include, so
> that files that userland programs would find with
> relative-to-/usr/include paths have to be modified for building in the
> tree.
>
> Was this conscious, or does anyone else think it would be smoother to
> -I include/ so that outside-the-tree and inside-the-tree #includes are
> more similar?
(and Mr. Lang points out that, of course, I really mean something like
-I $(srcdir)/include, of course)
next prev parent reply other threads:[~2012-11-02 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 21:14 include/ and -I Dan Mick
2012-11-02 23:35 ` Dan Mick [this message]
2012-11-03 19:01 ` Sage Weil
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=509458B8.8070709@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.