Cross compile UHD for powerpc

I am trying to cross compile UHD for a ppc embedded target (an e500 cpu)
but
I’m running into issues with cmake. It seemingly keeps defaulting back
to
the local build tools rather than the crosstools ng toolchain. Has
anybody
had success with this?

I’ve built UHD and gnuradio on an arm platform before (but not cross
compiling). I may try and get a native toolchain working on the powerpc
platform and work from there.

-Phelps

On 04/10/2011 05:48 PM, Phelps W. wrote:

I am trying to cross compile UHD for a ppc embedded target (an e500 cpu) but
I’m running into issues with cmake. It seemingly keeps defaulting back to
the local build tools rather than the crosstools ng toolchain. Has anybody
had success with this?

This may be helpful http://www.itk.org/Wiki/CMake_Cross_Compiling

I have never had the chance to build/run uhd on a non x86 architecture,
especially since apple switched over. This should be interesting.

-Josh

On 04/10/2011 05:48 PM, Phelps W. wrote:

I am trying to cross compile UHD for a ppc embedded target (an e500 cpu) but
I’m running into issues with cmake. It seemingly keeps defaulting back to
the local build tools rather than the crosstools ng toolchain. Has anybody
had success with this?

I’ve built UHD and gnuradio on an arm platform before (but not cross
compiling). I may try and get a native toolchain working on the powerpc
platform and work from there.

What powerpc target? As in what board? If there is support for the
machine in OE, it should be easy to construct an image with uhd in it.

Philip

I believe I managed to get UHD building properly, I’ll post more details
when I know for sure (haven’t fully tested yet). One thing I’ve run
into
however is that the gnuradio configure script doesn’t allow the uhd path
to
be specified (ie --with-uhd[=PATH]). This should probably be fixed.

Setting PKG_CONFIG_PATH to the uhd build directory did the trick.

-Phelps

On 04/12/2011 07:58 PM, Phelps W. wrote:

I believe I managed to get UHD building properly, I’ll post more details

cool!

when I know for sure (haven’t fully tested yet). One thing I’ve run into
however is that the gnuradio configure script doesn’t allow the uhd path to
be specified (ie --with-uhd[=PATH]). This should probably be fixed.

I’m not familiar w/ this concept. I usually set the PKG_CONFIG_PATH to
help the gnuradio-configure find the header and library paths. What
would --with-uhd= do?

-Josh

I ran into a speed bump here. I am getting an error when trying to
import
gr. It is looking for a module called _gruradio_core_runtime.

from gnuradio import gr
Traceback (most recent call last):
File “”, line 1, in
File
“/test/output/lib/python2.5/site-packages/gnuradio/gr/init.py”,
line 43, in
from gnuradio_core import *
File
“/test/gnuradio/output/lib/python2.5/site-packages/gnuradio/gr/gnuradio_core.py”,
line 23, in
from gnuradio_core_runtime import *
File
“/test/gnuradio/output/lib/python2.5/site-packages/gnuradio/gr/gnuradio_core_runtime.py”,
line 6, in
import _gnuradio_core_runtime
ImportError: No module named _gnuradio_core_runtime

With a build that is installed and working on my host machine, I look
into
/usr/local/lib/python2.6/dist-packages/gnuradio/gr and I see
_gnuradio_core_runtime.la
_gnuradio_core_runtime.so

In the cross compiled version of the same directory I don’t see
_gnuradio_core_runtime.so only _gnuradio_core_runtime.la. Could this be
causing this issue? Unlike my working x86 build I don’t have any shared
object files in the cross compiled build. Why is this? Am I missing a
configuration option or is there something that could cause the shared
objects not to be built?

Any ideas what could cause this import error?

-Phelps

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs