On 01/10/2023 01:06, Nic Bretz wrote:
Thanks for taking the time to reply. Frankly, I don't know what I
don't know, even after hours of online searches.
I've never seen an instance in an IDE where some folders are
displaying and others, at the same level, are not. For somebody like
me, new to GNU radio and CB, it's impossible to know if the issue is a
quirk of the IDE or the software.
I've chosen CB because that's what I read about in the wiki. I tried
VS Code but I couldn't get it to build, let alone run. At least CB builds.
The GNU Radio wiki is quite informative. For users. There is hardly
anything in there for developers. I know, we figure out things,
eventually. Except when we get stuck and run in circles. I spent hours
of my spare time trying to get basic things to work, hours that I
actually wanted to spend on algorithms.
Since Gnu Radio is *primarily* a *development framework* for developers
of signal-processing software, one could argue
that the entirety of the documentation is aimed at developers. I'll
just pick some random examples:
https://wiki.gnuradio.org/index.php/BlocksCodingGuide
https://wiki.gnuradio.org/index.php?title=Creating_C%2B%2B_OOT_with_gr-modtool
https://wiki.gnuradio.org/index.php?title=Creating_Your_First_Block
Gnu Radio uses a bunch of underlying tools, like C++ and its compilers,
Python, CMake, make, pybind11, etc, etc, etc. What
you WONT find is detailed tutorials on each of those tools within the
Gnu Radio documentation hierarchy. Information on each
of those tools is better served in other forums, and, like most Open
Source projects, Gnu Radio has limited resources. It would be,
quite honestly, wasteful of those resources to provide detailed
tutorials on each of the tools that the Gnu Radio project uses.
I don't know why Code::Blocks isn't "seeing" the Gnu Radio code tree.
That, I'm nearly 100% certain, isn't the fault of
the Gnu Radio code tree. There's nothing particularly "special"
about it. It is, after all, just a hierarchy of files, like
any other file hierarchy in the history of ever. If your editor of
choice cannot see that hierarchy, it is likely not the
fault of said hierarchy, at least, in my experience.
Anyway, sorry for the rant.
*From:* discuss-gnuradio-bounces+ayodha=hotmail@gnu.org
on behalf of
Marcus D. Leech
*Sent:* Saturday, September 30, 2023 9:11 PM
*To:* discuss-gnuradio@gnu.org
*Subject:* Re: Code::Blocks and FIR pm_remez algorithm
On 30/09/2023 22:42, N B wrote:
Helo,
I was looking at the FIR algorithm in pm_remez.cc and saw it is based
on the old Janovetz implementation of Parks-McClellan. The author of
one of my DSP books, Andreas Antoniou, makes the statement that he
improved on the original Parsk-McClellan algorithm. I found another
paper online where the author makes a similar statement.
I have no idea how accurate those statements are, but I am going to
experiment with those algorithms. I'll make those initial experiments
outside GNU Radio and if something good ever comes out of it, I would
like to modify pm_remez.cc with the new algos, even if only for my
personal use.
I'm getting to my issues, which I guess are really basic, but I'm new
to Code::Blocks.
I created the .cbp file and opened the project in Code::Blocks. I was
trying to trace the entire path from gr_filter_design to pm_remez.cc
and wasn't getting anywhere.
When I look under the folder gr-filter, I see only two subfolders,
lib and python. Eventually I looked in Github and there I could see
several more subfolders under gr-filter, which I don't have in CB. (I
couldn't be more grateful for the ability to search definitions and
references in Github. I was able to trace the entire path in a few
minutes)
My questions in order of importance are:
Why don't those folders display in CB?
Is it possible to Run the entire project in CB? It builds fine, but
it just doesn't run.
Thanks,
Nic
Your question is a bit like asking George Lucas why the BluRay copy of
Episode IV won't play in your machine
This isn't the Code::Blocks support mailing list, so my guess is that
your question would be better asked in a more appropriate
group. There are literally *dozens* of editing/IDE environments
that people use to work on Gnu Radio code.
