[Top][All Lists]

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

Re: [Discuss-gnuradio] Building with CMake on Win7 with MSVC 2008

From: Josh Blum
Subject: Re: [Discuss-gnuradio] Building with CMake on Win7 with MSVC 2008
Date: Wed, 12 Dec 2012 09:06:24 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0

On 12/12/2012 07:40 AM, wakjah ' wrote:
> OK, so here's what I've done to get it to build:
> - To build gnuradio-core, comment out lines in
> D:\gnuradio\src\gnuradio-3.3.0\gnuradio-core\src\lib\io\CMakeLists.txt
>     #${CMAKE_CURRENT_SOURCE_DIR}/gr_stream_pdu_base.cc
>     #${CMAKE_CURRENT_SOURCE_DIR}/gr_stream_pdu_base.h
>     #gr_tuntap_pdu
>     #gr_socket_pdu
> - Remove
>     #include <gr_pdu.h>
>     #include <gr_tuntap_pdu.h>
>     #include <gr_socket_pdu.h>
>     %include "gr_pdu.i"
>     %include "gr_tuntap_pdu.i"
>     %include "gr_socket_pdu.i"
> from D:\gnuradio\src\gnuradio-3.3.0\gnuradio-core\src\lib\io
> It seems that these new modules (added to git 5 days ago) don't play nicely
> with CMake on windows (the libraries required only exist on Linux anyway)

It seems like some unstable stuff was merged into master. Can you post
the error? I understand the tuntap issue. But I'm not sure about the

> - To build gnuradio-audio, add #include <io.h> to audio_portaudio_source.cc
> and audio_portaudio_sink.cc

can you post the patch?


> - Add boost.Chrono library input to linker missing from projects:
> fcd_nfm_rx
> dial_tone
> _filter_swig
> _fft_swig
> _fcd_swig
> _pager_swig
> _digital_swig
> _vocoder_swig
> _blocks_swig
> _audio_swig
> _analog_swig
> With these modifications, it builds on MSVC 2008.

Interesting, I think one of the boost dependencies pulls in another
boost dependency that we dont normally link against. My reference is
boost 1.47.

What version of boost are you using?

Can you post the patch for this?

> I am now getting issues with RUN_TESTS - they all seem to fail. However,
> after running the INSTALL build and testing in Python, it seems like most
> things work. How can I ascertain the causes of these test failures?

Usually its an issue of something missing from the %PATH%. The test
scripts attempt to set the environment variables so that in-tree build
products are in the PATH, but probably not out of tree dependencies. It
may be good to run dependency walker and see what is "missing"

> My main objective with this was to get the portaudio source working - I
> believe this was not compiled with the precompiled binaries from Ettus
> Research, which is what started me off compiling in the first place. The
> audio sink appears to work fine, but the audio source does not:
> audio_copy.py simply exits after the call to run(), without an error

I think the windows audio source implementation is empty!

> message (there are a couple of complaints about invalid arguments to
> gr_vmcircbuf_default_factory, but that usually doesn't stop the whole thing
> from working). Does anyone know how I can debug this?

That print is safe to ignore.


reply via email to

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