[Ground-station] Fwd: [Discuss-gnuradio] [RFNoC] Transition of branch from rfnoc-devel to master

[Michelle Thompson]

RFNoC updates in GNU Radio.

-Michelle W5NYV



---------- Forwarded message ----------
From: Martin Braun <martin.braun at ettus.com>
Date: Mon, Jul 9, 2018 at 10:47 AM
Subject: [Discuss-gnuradio] [RFNoC] Transition of branch from rfnoc-devel
to master
To: "USRP-users at lists.ettus.com" <usrp-users at lists.ettus.com>, "
discuss-gnuradio at gnu.org" <discuss-gnuradio at gnu.org>


Hi all,

we have recently been working more on the RFNoC side of things, and
there's some updates I want to bring to you.

The first step we did to a more stable version of RFNoC is merging all
of the work on rfnoc-devel back into master. This will make it a lot
easier to keep features in sync between RFNoC and regular/vanilla UHD.
Going forward, we will no longer push updates to the rfnoc-devel
branches, and at some point we will delete those branches in favour of
master (for now, we'll leave them up so people following the existing
instructions won't get an error, but they will be frozen as of now).

For those of you who aren't actively developing on RFNoC, there is no
difference (with the exception of E310 users, but I'll send out another
email on that in a bit).
For people playing with RFNoC, keep the following things in mind:

- Anytime you read something referencing the rfnoc-devel branch, simply
change that to master branch.
- The RFNoC APIs are still disabled by default, and require using the
-DENABLE_RFNOC=ON CMake switch to use them
- If you have patches on top of rfnoc-devel, you may want to rebase them
on top of master. They should cleanly apply, as of now, the diff between
the two branches is minimal.

Why do we require the `-DENABLE_RFNOC=ON`? The reason is, the APIs are
not covered by our guarantee that we won't change them (in case you were
unaware, we have a strong guarantee that we won't change APIs unless we
also change the API version number, i.e., all 3.11.* releases have the
same API). Think of setting that switch as a waiver that says "I have
understood that I am using APIs that do not have a strong guarantee of
being unchanged".

On the FPGA branch, there is no such CMake switch, and the same branch
will server RFNoC and non-RFNoC users alike.

Thanks all!

Martin

_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio at gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openresearch.institute/pipermail/ground-station-openresearch.institute/attachments/20180709/8345aa37/attachment.html>