[Top][All Lists]

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

Re: [Discuss-gnuradio] Compiling GNU Radio - Debian unstable

From: Eric Blossom
Subject: Re: [Discuss-gnuradio] Compiling GNU Radio - Debian unstable
Date: Thu, 10 Apr 2003 20:18:49 -0700
User-agent: Mutt/1.4i

On Thu, Apr 10, 2003 at 10:25:04PM +0200, Guillaume Leclanche wrote:
> I encountered many issues, and I've reached a threshold, I now have only a 
> pure compilation issue ;-) It's like an assault course.

Sorry about that...
Thanks for letting me know about the problem.

> Here is my experience:
> At first I downloaded the CVS, from which i didn't manage to extract a clean 
> configure script, therefore I gave up and downloaded 0.7.

Please let me know which OS and version you're using.
Try $ uname -a

> My first trial was to find the right versiion of Qt for the configure test. 
> I tested many, and many combination of dirs, and in the end, it became 
> obvious that QT3 was necessary, because the moc refuses to compile the 
> software if you use QT2 libs.

In my environment it does work under Qt2, so I'm not exactly sure what
the problem is.   By any chance do you have both Qt2 and Qt3
installed.  Perhaps configure was picking the wrong version of moc.

> I had also an error that held me some days wondering what I could do, until 
> I understood that the includes in some GNU Radio Qt files were very old 
> files (Qt1 headers ?). I downloaded the source package of libqt2-dev, and i 
> found inside it a dir names "compat", which was containing every missing 
> file I needed. I copied them inside my /usr/include/qt3, and there I went 
> further :-)

I'll take a look at any old stuff and see if I can figure out what
needs to be updated.  If you've got any suggestions, I'd be delighted
to hear about them.

FWIW, the Qt stuff has been a bit of pain to configure.
Eventually it will be all removed, and all the GUI stuff will be
accessed through what every GUI tools are available in your scripting
language of choice.  (I know that that doesn't help your problem today...)


reply via email to

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