Old Pybombs14.04 LTS (you know stable stuff)
Installing packages:
* gr-fcdproplus
Installing from source: gr-fcdproplus
 
    CC=gcc CXX=g++ cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo 
-DCMAKE_INSTALL_PREFIX=/home/gratcliff/Downloads/target $config_opt

CMake Error at CMakeLists.txt:32 (cmake_minimum_required):
  CMake 3.0 or higher is required.  You are running version 2.8.12.2


cmake 3 won't likely come to and LTS packages for a while.
Thanks in advance,
Greg Gregory W. Ratcliff






 
      From: Jose Ruvalcaba <joruv...@gmail.com>
 To: discuss-gnuradio@gnu.org 
 Sent: Monday, April 4, 2016 7:41 PM
 Subject: [Discuss-gnuradio] Trying to build a DVB-S2 LDPC decoder
   
Hello,I am new to GNU radio and to SDR's and I am trying to implement a DVB-S2 
LDPC decoder block that can be used with the LDPC DVB-S2 encoder available in 
GNU radio. I have been able to write an LDPC decoder which uses a 16,200 long 
parity check matrix used only for a DVB-S2  short frame, rate = 1/4 code. The 
problem is that when running my written block it's taking a long time to decode 
one iteration of data(about an hour long). I was wondering if anyone has any 
advice in how to go about writing code for FEC blocks, especially LDPC codes, 
which will be used in GNU radio and eventually in an SDR? In other words, are 
there certain libraries that should be used when trying to write FEC decoders 
in gnu radio? How could I make a GNU radio FEC block which takes in a codeword 
length 16,200, like the one in DVB-s2, to work in a USRP? Is it smart to make 
my large (12960 x 16,200) parity check matrix using the standard 'vector' 
library in C++?   Any advice, tips and suggestions will be greatly 
appreciated.Thanks,
Jose

_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


   
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to