Is there a recommended or preferred way an application should check
for the availability of control port? I can see some #ifdef
GR_CTRLPORT in the gnuradio headers but that is only defined while
compiling gnuradio. If there is a safe check I could perform at cmake
time I would prefer that.
Thanks in advance.
On Fri, Mar 29, 2013 at 8:12 PM, Alexandru C. [email protected]
wrote:
Is there a recommended or preferred way an application should check
for the availability of control port? I can see some #ifdef
GR_CTRLPORT in the gnuradio headers but that is only defined while
compiling gnuradio. If there is a safe check I could perform at cmake
time I would prefer that.
Thanks in advance.
Alex
Hi Alex,
Good question. This is what the config.h file is for. It’s installed
into $prefix/include/gnuradio/config.h. If ControlPort is defined and
built for the project, it will be defined in this file as “#define
GR_CTRLPORT”. If you include that header file, you can test #ifdef
GR_CTRLPORT in your own work.
Good question. This is what the config.h file is for. It’s installed
into $prefix/include/gnuradio/config.h. If ControlPort is defined and
built for the project, it will be defined in this file as “#define
GR_CTRLPORT”. If you include that header file, you can test #ifdef
GR_CTRLPORT in your own work.
Hi Tom,
Thanks for the reply. This will work for me, but it seems some cmake
magic is missing from the build procedure because GR_CTRLPORT is not
defined in the config.h that I have. Here are the contents:
Actually, it looks like Tim is right. I always do fresh builds with
clean directory. If I add the -DENABLE_GR_CTRLPORT=TRUE then config.h
will contain the #define GR_CTRLPORT otherwise it will not. This works
fine for me for now.