From: Erwin Authried <eauth@softsys.co.at>
To: "bluez-users@lists.sourceforge.net" <bluez-users@lists.sourceforge.net>
Subject: Re: cross-compilation howto (was "Re: [Bluez-users] Trying to compile for axis but Bluetooth library not found")
Date: Fri, 04 Feb 2005 19:19:03 +0100 [thread overview]
Message-ID: <1107541143.22567.29.camel@justakiss> (raw)
In-Reply-To: <4203B1BB.1070006@gmx.ch>
Am Fre, den 04.02.2005 schrieb Marco Trudel um 18:32:
> Hello Marcel
>
> I learned a lot of configure and make flags I didn't knew before.
> So, that's the state:
>
> For crosscompiling, it's enought to:
> ./configure --build=[buildArchitecture] --host=[targetArchitecture]
>
> The cross-compiler has to be in path.
> That's it. Everything else is like usual compiling.
>
Hi,
you are almost right. In practice, almost every configure script has
some problems with cross-compiling. For example, configure scripts that
do runtime tests for the target system will obviously fail. You can work
around that by supplying a hand-crafted config.guess that substitutes
missing values. In other cases, you have to play with configure options
and environment variables.
> I don't think this is worth a howto, do you?
> Actually a bluetooth compilation howto with a little crosscompiling
> subsection that hints to the --build and --host switches should be more
> than enough.
It's definitely worth to have a howto, because if you search the web or
mailinglists, there are a lot of misleading or wrong hints regarding
this topic. I don't have time right now to write a howto, but I think
that the recent postings are already some help to get started for
somebody who is in trouble with cross-compiling.
>
> Erwin: Is only using --host proper?
> It works but I get a warning (I don't like warnings. So I always try to do
> things right.)
>
I have cross-compiled a lot of packages, and --host was always
sufficient (I tried to use the possible minimum of options) . The
warning says:
"WARNING: If you wanted to set the --build type, don't use --host."
that applies to something that you don't want to do anyway in our case.
Regards,
Erwin
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-02-04 18:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 19:23 [Bluez-users] Trying to compile for axis but Bluetooth library not found joe sloan
2005-01-31 20:51 ` Erwin Authried
2005-02-01 10:07 ` Joe Sloan
2005-02-01 10:36 ` Marcel Holtmann
2005-02-01 14:19 ` Marco Trudel
2005-02-01 14:36 ` [Bluez-users] cross-compilation miniHowto, first change Marco Trudel
2005-02-01 14:42 ` [Bluez-users] Trying to compile for axis but Bluetooth library not found Marcel Holtmann
2005-02-01 15:12 ` Marco Trudel
2005-02-01 15:20 ` Marcel Holtmann
2005-02-01 15:22 ` Marco Trudel
2005-02-01 15:47 ` Marcel Holtmann
2005-02-01 15:59 ` Erwin Authried
2005-02-04 17:32 ` cross-compilation howto (was "Re: [Bluez-users] Trying to compile for axis but Bluetooth library not found") Marco Trudel
2005-02-04 17:38 ` Marcel Holtmann
2005-02-04 23:20 ` Marco Trudel
2005-02-05 0:05 ` Marcel Holtmann
2005-02-04 18:19 ` Erwin Authried [this message]
2005-02-04 18:22 ` Marcel Holtmann
2005-02-04 18:31 ` Marco Trudel
2005-02-04 18:38 ` Erwin Authried
2005-02-04 18:43 ` Marcel Holtmann
2005-02-04 18:55 ` Erwin Authried
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=1107541143.22567.29.camel@justakiss \
--to=eauth@softsys.co.at \
--cc=bluez-users@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 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.