From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] building OpenNI with ptxdist
Date: Fri, 20 Jan 2012 10:33:46 +0100 [thread overview]
Message-ID: <3f3a08f178c34f5431162bdff0c64b7b@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <9aa177152ed039e1e18f4d7b6c2ebd6f@idefix.lespocky.dyndns.org>
Some progress on this topic:
Am 19.01.2012 15:37, schrieb Alexander Dahl:
> For doing this without ptxdist I create a folder ~/build/sysroot and
> tried cross compiling. Doing it like in the README this results in an
> error stating 'unistd.h' is not found. If I copy the content of
> /opt/OSELAS.Toolchain-2011.03.0/arm-v5te-linux-gnueabi/gcc-4.5.2-glibc-2.13-binutils-2.21-kernel-2.6.36-sanitized/sysroot-arm-v5te-linux-gnueabi
> to ~/build/sysroot/ first, compiling succeeds (after manually cross
> compiling libusb and installing it to ~/build/sysroot).
I asked on the OpenNI mailing list [1] and it seems this will get ugly
because of patching their Makefiles with fixed path to the toolchain
lets my hackles raise. I guess there's no way of »dynamic patching«
depending on environmental things, I would have to hack something in the
extract rule maybe to not have fixed pathes in my patches.
To make a long story short, I'll see if the OpenNI community has
further ideas how to build this before starting a rant of using a cross
compile aware build system. ;)
Greets
Alex
[1]
https://groups.google.com/group/openni-dev/browse_thread/thread/7a9d1afc8c7cfbd1
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2012-01-20 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 14:37 Alexander Dahl
2012-01-20 9:33 ` Alexander Dahl [this message]
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=3f3a08f178c34f5431162bdff0c64b7b@idefix.lespocky.dyndns.org \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.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