linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: yegorslists@googlemail.com
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org
Subject: Fix out-of-source build breakage
Date: Wed, 28 Dec 2011 10:53:35 +0100	[thread overview]
Message-ID: <1325066017-2384-1-git-send-email-yegorslists@googlemail.com> (raw)

These patches fix out-of-source build breakage. The first one fixes
link creation and the second one adds tools to includ folder list.

The patches were tested for both in-source and out-of-source scenarios.

Following patch was included in this patch set and can be ignored:
[PATCH] fix lib header linking for out-of-source build

Yegor

             reply	other threads:[~2011-12-28  9:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28  9:53 yegorslists [this message]
2011-12-28  9:53 ` [PATCH 1/2] fix link creation for out-of-source builds yegorslists
2011-12-28  9:53 ` [PATCH 2/2] add tools to include folder list yegorslists
2011-12-28 17:41 ` Fix out-of-source build breakage Marcel Holtmann
2011-12-29  8:10   ` Yegor Yefremov

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=1325066017-2384-1-git-send-email-yegorslists@googlemail.com \
    --to=yegorslists@googlemail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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 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 NNTP newsgroup(s).