On Wed, Feb 10, 2016 at 2:50 PM, Jacob Gilbert <[email protected]>
wrote:
> Tom -
>
> So as it turned out, I had the rpcbasic_register_set<> value types
> mismatched (signed vs unsigned) and that error was hidden within a huge
> mess of errors that appeared to be "could not find rpcbasic_register_set"
> errors. Sorry for the confusion.
>
Great! And don't you love debugging with C++ templates?
> Thank you for the #include. That builds with GR_CTRLPORT set. Are there
> any recommendations for what the "suggestion" pmt's should be for
> string-type values?
>
> Thanks
>
Excellent.
As for the suggestions, they are mostly for the client side to set up
limits and what they should expect to see. It's a very loosely defined
concept. For your part, you're probably ok just leaving these as empty ("")
PMT strings.
Tom
>
> On Wed, Feb 10, 2016 at 11:42 AM, Tom Rondeau <[email protected]> wrote:
>
>> On Wed, Feb 10, 2016 at 11:37 AM, Jacob Gilbert <
>> [email protected]> wrote:
>>
>>> I'm having some trouble adding ControlPort hooks to an OOT module. Is
>>> there a guide on this I am missing? I followed the ControlPort manual page
>>> including the #ifdef statements, however GR_CTRLPORT is not set and the
>>> controlport code never gets built.
>>>
>>
>>
>> For this, use:
>>
>> #include <gnuradio/config.h>
>>
>> That file defines GR_CTRLPORT (if it's been enabled in GNU Radio).
>>
>>
>>
>>> If I force the code to be built, the build fails as none of the
>>> controlport stuff is included. There appears to be some CMake or include
>>> statements I am missing. I tried to modify the top-level/lib/swig cmake
>>> files to emulate what in-tree modules have done but to no avail.
>>>
>>> ControlPort and thrift are definitely built into the GR installation and
>>> works just fine. Any pointers are appreciated. GR is release 3.9.2
>>>
>>> Thanks, Jacob
>>>
>>
>>
>> Can you post the error you're seeing? All ControlPort functionality is
>> built into gnuradio-runtime, which you should be linking against by default
>> in any gr_modtool project. But yeah, the actual error will help narrow this
>> down to what the real problem is.
>>
>> Tom
>>
>>
>
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
