Re: [Discuss-gnuradio] Help with building GNU Radio for Android

Although, now that I think about it, there's no reason to SWIG gr-grand. You'll never use that in Python on Android; we only use the c++ library out, and specifically the static libgnuradio-grand.a library.

Maybe try adding the flag -DENABLE_PYTHON=False to the cmake line?

ENABLE_PYTHON is not an available option, and there is no option to disable Python or SWIG (the cmake user settable variables can be listed using -LAH).

Are you sure you want armv7-m? Most of what we're using is armv7-a. But you might just try "armv7" instead to use a more generic v7 architecture. Take a look at the gcc man page for a list of supported machines. This might be something you'll need to play around with.

I made a mistake in copying the error, here is the correct error.

Assembler messages:

Fatal error: invalid -march= option: `armv7-a'

I was able to get Boost to build. The problem is that when arm-linux-androideabi-g++ calls the assembler it looks in the path for as the problem with this is that the assembler for Android is named arm-linux-androideabi-as . To fix this I symlinked arm-linux-androideabi-as to as and android-toolchain/bin needs to be in your path (it should be from setting up the android toolchain). However this must be done after running bootstrap.sh or Boost will fail to build Boost.Build. Running hash -r may be required to get bash to find the correct assembler.

The real problem here is that android-toolchain/arm-linux-androideabi/bin/ is empty and not symlinked to the tools in android-toolchain/bin/ like it normally is. I have tried rebuilding the toolchain multiple times, but it is not making the symlinks. I just copied the symlinks from OS X and it works on Ubuntu 14.04 (tested for FFTW).

Yeah, when this is right, you should see 'yes' for 32-bit and arm.

That is what I got when using OS X with Boost and specifying toolset=gcc-android .

How hard would it be to get fosphor working on Android?

Schuyler, there might have been a change in something in Android (they really don't care about changing things between versions) when building the standalone SDK. Take a look at the options you passed when building that part of the project. Also, make sure you are using GCC 4.8 and NOT 4.9. We have other issues with 4.9.

I am using GCC 4.8.