From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez-utils-3.0 cross compile broken
Date: Sat, 17 Jun 2006 12:31:05 +0200 [thread overview]
Message-ID: <1150540265.17539.26.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0606131329100.23668@redbean.intranet.gw-instruments.de>
Hi Peter,
> > the bluez-utils-3.0 is now using pkg-config for the library detection.
>
> What a pain ...... I'll stay with the older version for now ......
> When I got some spare time I'll try to figure out how to use this stuff
> when doing cross builds.
sorry for that, but pkg-config should actually make it easier in the
end. And a new major version is allowed to break stuff :)
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-17 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 9:22 [Bluez-devel] bluez-utils-3.0 cross compile broken Peter Wippich
2006-06-13 11:10 ` Marcel Holtmann
2006-06-13 11:36 ` Peter Wippich
2006-06-17 10:31 ` Marcel Holtmann [this message]
2006-06-18 13:02 ` Peter Wippich
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=1150540265.17539.26.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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