Name                               Last modified       Size  Description

 Parent Directory                   13-Jan-2006 16:12      -  
 Changelog                          20-Feb-2006 11:28     1k  
 broken/                            25-Jan-2006 04:30      -  
 built-2.6cvs/                      10-Jun-2006 23:25      -  
 gnuradio-examples-0.5.tar.gz       31-Oct-2008 00:41   190k  
 readme                             10-Jun-2006 23:52     5k  
 required-for-build-from-source/    10-Jun-2006 23:18      -  
 seperate-2.6cvs/                   25-Jan-2006 04:11      -  
 setup-gnuradio-complete-2.6cvs.exe 20-Feb-2006 10:13   7.7M  
 source-2.6cvs/                     10-Jun-2006 23:24      -  

#
# README gnuradio for windows 
# binary installer
#

Because of the many requests I hereby give you the preliminary binary installers of gnuradio for windows.
This is not finished work, but now you can start to play with it.

Installation instructions:
make sure Python 2.4.1 for windows is installed
also install wxpython
(from the python website site download: python-2.4.1.msi, wxPython2.6-win32-ansi-2.6.0.0-py24.exe)

install the following executable
setup-gnuradio-complete-2.6cvs.exe

This will install gnuradio-core gr-audio-windows gr-wxgui gr-usrp usrp

You can also install the individual parts seperately.
Look in the seperate directory for the individual installers

All the gnuradio python files are put in C:\Python24\Lib\site-packages
The usrp driver is installed in C:\Program Files\Usrp
C:\Program Files\Usrp\bin is put onto your PATH to enable windows to find the usb driver
The environment variable USRP_PATH is set to C:\Program Files\Usrp
The driver uses this to find the the usrp_fpga.rbf firmware which is in
C:\Program Files\Usrp\rev2\usrp_fpga.rbf


How to use gnuradio on windows:
open a windows command prompt

Make sure C:\Python24;c:\Python24\DLLS;C:\Python24\libs is on your path

Try any one of the gnuradio examples in gnuradio-examples-*.tar.gz (download from main gnuradio website)
You can do for example:
tar zxvf gnuradio-examples-0.x.tar.gz (you can also untar this with winzip, 7zip or winrar)
cd gnuradio-examples-0.x\python\audio
python dialtone.py
cd ..
cd gnuradio-examples-0.4\python\usrp
python usrp_rx_file.py
python test_counting.py
python usrp_wfm_rcv.py

If you get wxgui errors with the graphical examples you should put the following two lines in the top of these files:
import wxversion
wxversion.select('2.6')

If you don't have a powermate then remove the import powermate statements from the examples
Otherwise you will get errors like:
>python usrp_wfm_rcv.py
Traceback (most recent call last):
  File "usrp_wfm_rcv.py", line 8, in ?
    from gnuradio.wxgui import slider, powermate
  File "D:\Python24\Lib\site-packages\gnuradio\wxgui\powermate.py", line 30, in
?
    import fcntl
ImportError: No module named fcntl

I don't know if they will work WITH a powermate because I don't have one to test with.


Uninstall:
You have to uninstall all parts seperately
Open Add/Remove programs control panel
You will find all python uninstallers under Python 2.4
Python 2.4 usrp_prims        (python part of the usrp dirver)
Python 2.4 gr-usrp           (glue between usrp driver and gnuradio)
Python 2.4 gnuradio-core     (core of gnuradio)
Python 2.4 gr-audio-windows  (audio driver for gnuradio for windows)
Python 2.4 gr-wxgui          (graphics part (wxwindows) for gnuradio )

Further you will find:
Gnuradio 2.6cvs              (this is only this Readme)
Usrp 0.10cvs                  (the usrp libusb driver and firmware)

Known Bugs:
The first time you start an usrp executable you get an error about not being able to attach to an interface.
After this first run the error should be gone.

(null)/.gnuradio/prefs/gr_vmcircbuf_default_factory: No such file or directory
This warning is because gnuradio is trying to open the defaults file in a unix style homedirectory.
Windows dows not have those so this warning is shown.
The net result is that gnuradio will determine your circbuf factory on every invocation in stead of only once.
It should still work though, although it will start a bit slower.


For developers:
In built-2.6cvs you will find tarfiles from all the built sources, These include  all the lib.a files, include files, object files , dlls and executables as a result of the complete built sources.
So if any dll or other file is missing in this installer you can find it there
You also need these if you start developing your own C or C++ code and don't want to built gnuradio and all required libs from source yourself.

In source you will find the sources which where used to built these files.

In required-for-build-from-source you will find the binaries from the tools and libraries I used to build gnuradio and usrp (all needed dlls, executables, libraries (libXXX.a) and  include header files should be in the tarballs.)

You can use these if you want to build gnuradio or usrp yourself using msys and mingw.
You might also need these if you build your own C or C++ files using the gnuradio and/or usrp libraries.

A more save method is building all these libraries yourself. Esppecially cppunit is picky when it comes to mixing different gcc versions.

bin/build_all_windows_installers_cvs.sh is the top script which is used to build the installers from the built sources.

There are some hardcoded paths in there so you may have to change these for your setup.
You also need to have innosetup installed if you want to built everything.
When the main script launches innosetup you just need to command it to do the compile and close it.
After that the built script will continue
(The script will do this twice)


Success,
Martin Dudok van Heel    ,June 2006 
nldudok1 at olifantasia com