Cross compiling on a Raspberry Pi... about nanovna-h HOT 2 OPEN

I have successfully run the current version "remotely " on Raspberry 3B, using Terminal Communication Framework (TCF) plug-in on Eclipse.
I have used unmodified Makefile and no other complier / linker modification.

Since this seems to be ONLY place where developers gather I would like to ask here.If it is OK.

I like to add ability to output debugging messages to standard i/o console.
I do not have NanoVNA hardware and do not intend to actually run the software on it anyway.
I just want to be able to trace / debug using prinff or cout.

I should be able to add required code to Makefile, but I am not sure how,

I'll look into TCF debugging abilities for now.

from nanovna-h.

I am really reluctant to post this here.
I am finding out that there is NO forum / group dedicated to NanoVNA SOFTWARE development.
The "development" is scattered on each individual "enterpriser" using whatever format / forum - if any.

I am of an opinion that nobody is really interested in NanoVNA as a common project.
Even this one is focused on fixing issues, which is fine.
What is really puzzling - the purpose of git(hub) is to share code.

How can I share code if I cannot physically test it ?
I have not found a way to run perfectly working NanoVNA code in debug mode.
I'll keep trying.

from nanovna-h.