From: Marcel Holtmann <marcel@holtmann.org>
To: yegor_sub1@visionsystems.de
Cc: linux-bluetooth@vger.kernel.org, johan.hedberg@gmail.com
Subject: Re: bluez-4.97: check dependnecy
Date: Fri, 23 Dec 2011 09:05:35 -0800 [thread overview]
Message-ID: <1324659935.1965.259.camel@aeonflux> (raw)
In-Reply-To: <4EF4582E.6020308@visionsystems.de>
Hi Yegor,
> I was cross compiling bluez-4.97 under Buildroot and with the same configuration as for 4.96 configure failed by not being able to find check framework. Could this dependency be dropped if I don't want to compile tests? I mean it doesn't make much sense using check on x86 build host for arm binaries.
yes, it can be dropped. We only need that for development. Care to send
a patch for it.
Regards
Marcel
next prev parent reply other threads:[~2011-12-23 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 10:30 bluez-4.97: check dependnecy Yegor Yefremov
2011-12-23 17:05 ` Marcel Holtmann [this message]
2011-12-28 8:36 ` Yegor Yefremov
-- strict thread matches above, loose matches on Subject: below --
2012-01-02 20:50 nello martuscielli
2012-01-02 20:58 ` nello martuscielli
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=1324659935.1965.259.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yegor_sub1@visionsystems.de \
/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).