[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] compiling atsc_trellis_encoder.cc
From: |
Charles Swiger |
Subject: |
Re: [Discuss-gnuradio] compiling atsc_trellis_encoder.cc |
Date: |
Tue, 11 Apr 2006 09:52:24 -0400 |
On Mon, 2006-04-10 at 17:26 -0400, Charles Swiger wrote:
> I'm getting this error compiling a new file in atsc, copied from
> atsc_rs_encoder.cc:
>
> atsc_trellis_encoder.cc:55: error: no matching function for call to
> `atsci_trellis_encoder::encode(atsc_data_segment&, const
> atsc_mpeg_packet_rs_encoded&)'
> ./atsci_trellis_encoder.h:50: note: candidates are: void
> atsci_trellis_encoder::encode(atsc_data_segment*, const
> atsc_mpeg_packet_rs_encoded*)
>
Spotted this difference - in a working compile atsci_data_interleaver.cc
the arguments are addresses:
atsci_data_interleaver::interleave (atsc_mpeg_packet_rs_encoded &out,
const atsc_mpeg_packet_rs_encoded
&in)
but in the failing compile atsci_trellis_encoder.cc
they are not:
atsci_trellis_encoder::encode (atsc_data_segment out[NCODERS],
const atsc_mpeg_packet_rs_encoded
in[NCODERS])
(thinking)
Oh OK - got it too compile by changing atsc_trellis_encoder.cc
from d_trellis_encoder.encode(out[i], in[i]);
to d_trellis_encoder.encode(&out[i], &in[i]);
Well, it compiles but there are likely still issues since the 0.9 work
function in GrAtscTrellisEncoder.cc has stuff to deal with an array
of encoders that I don't understand:
// We must produce output.size units of output.
for (unsigned int i = 0; i < output.size; i +=
atsci_trellis_encoder::NCODERS){
// primitive does 12 segments at a time.
// pipeline info is handled in the primitive.
encoder.encode (&out[i], &in[i + start]);
}
Guess I'll look at where output.size comes from and what start does.
--Chuck