discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss-gnuradio] Re: gr_python.m4


From: Martin Dvh
Subject: [Discuss-gnuradio] Re: gr_python.m4
Date: Mon, 11 Jul 2005 06:26:51 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030823

Eric Blossom wrote:
On Mon, Jul 11, 2005 at 01:38:43AM +0200, Stephane Fillod wrote:

I checked in a new version of gr_python.m4 that uses distutils to
determine the include path for Python.h.  I tested it on GNU/Linx and
OS/X and it works there.

It's not going to work for any cross-dev setup (eg. mingw under Linux)
because it's trying to run the xdev python:

       # ask distutils which include path we should use
       python_path=`$PYTHON -c "import distutils.sysconfig; \
               print distutils.sysconfig.get_python_inc(plat_specific=False)"`
I ran this line on my windows/mingw setup.
I got:
d:\Python24\include
I haven't checked if this works for building.
(I normally  use  the forward slash format for everything  which would be 
/d/python24/include )

The config.log of my last build on windows (with my version of the python 
macros, not this new one) shows:
configure:21246: checking for python version
configure:21253: result: 2.4
configure:21265: checking for python platform
configure:21272: result: win32
configure:21279: checking for python script directory
configure:21287: result: /d/Python24/Lib/site-packages
configure:21296: checking for python extension module directory
configure:21304: result: /d/Python24/Lib/site-packages
configure:21321: checking for Python include path
configure:21344: result: /d/Python24/include


Good point.

Cross development pretty much screws autoconf unless there's a way of
getting answers for the target environment.

So, then the question becomes, "what's the easiest way to build GNU
Radio for a windows target?"

I thought that most people ran MinGW under windows.  I take it that
you are running it under linux and generating windows binaries.
Perhaps a quicker path is just to make GNU Radio build under MinGW
running under windows?  Then the cross development issues go away.

Martin, do you use MinGW under windows, or are you cross developing
from GNU/Linux?
I am using MingW under windows.
(Never even tried cross-development from linux)

The important thing is to setup all dependencies right.
This means installing and building/installing a lot of libraries/tools.
install mingw
install msys
install python, wxpython  (standard windows binary versions, not mingw specific)
install python-win32 api (optional: for win32-named_pipes, only needed for 
fft-sink scope-sink)
build from source/install latest version of libtool
patch/buildfromsource/install fftw, cppunit
download boost-jam binary
buildfromsource/install boost

buildfromsource/install gnuradio-core
buildfromsource/install wxgui-win32
buildfromsource/install gr-aduio-windows

somehowinstall usrp stuff (no experience here)

use your favourite gnuradio python script

The only thing from the base-mingw/msys tools I upgraded is libtool.


Comments?

Eric







reply via email to

[Prev in Thread] Current Thread [Next in Thread]