[Discuss-gnuradio] Re: gr_python.m4

[Stephane Fillod]

On Sun, Jul 10, 2005 at 05:24:59PM -0700, 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)"`
> 
> Good point.
> 
> Cross development pretty much screws autoconf unless there's a way of
> getting answers for the target environment.

autoconf can work cross development, but extra care has to be taken :(

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

I would say natively. Since I'm a developer and not a Windows final
user, I'll be the only one doing cross-development.

> 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.

I'd like, if possible, to keep the ability to cross-build MinGW under
Linux. This is very handy to check the portabilty, from the same source
tree (VPATH), without having to reboot. I think this is possible cheaply
thanks to the autoconf cache and some ac_cv_* variable overload from the
configure line. I'll come up with a config/gr_python.m4.

Thanks
-- 
Stephane