Editing GNU Radio 4.0 Preliminary Code Review

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 3: Line 3:
; License
; License
: GPLv3 - probably don't have much choice here unless we want to have some parts under a different license (e.g. PMTF under lgpl)
: GPLv3 - probably don't have much choice here unless we want to have some parts under a different license (e.g. PMTF under lgpl)
; Git History
: Very divergent - do we start from scratch and let 3.x and 4.0 each have their own history


; Build System
; Build System
Line 14: Line 11:
: subprojects - CLI11, cpp-httplib, cppzmq, json, moodycamel, pmt
: subprojects - CLI11, cpp-httplib, cppzmq, json, moodycamel, pmt
: QA tests
: QA tests
* Domain specific blocks/buffers - e.g. CUDA
: Domain specific blocks/buffers - e.g. CUDA
** Don't have a good solution for making this out of tree but still cohesive (same block with multiple impl)
* Don't have a good solution for making this out of tree but still cohesive (same block with multiple impl)


; gnuradio-runtime --> gr namespace
; gnuradio-runtime --> gr namespace
Line 35: Line 32:
** Less scheduler "hints"
** Less scheduler "hints"
** Self contained work() function
** Self contained work() function
; Python Blocks
: block implementations
: arbitrary blocks


; Block Autogen
; Block Autogen
Line 44: Line 37:
: jinja templates
: jinja templates
: create_{mod,block} scripts
: create_{mod,block} scripts
; Block Porting
: what is involved and what can be automated?
: Options for shimming 4.0 blocks back into 3.x?


; Kernel Library
; Kernel Library
Line 61: Line 50:
; Benchmarking
; Benchmarking
: What to include in-tree
: What to include in-tree
; GRC
: Changes needed to support 4.0 features
: Plan to move out of tree??
: Start with QT port or off established GTK GRC?
; Coding Standard
: C++ modernization
: clang-format changes
: python/pep8 format changes
: enforce YAML, build system format checks?
: offer / encourage pre-commit hook usage (e.g. through [https://pre-commit.com/hooks.html this])
; Out-of-Tree / Ecosystem
: example OOT project
: modtool (successor? Extension? BW compat?)
: deb/rpm/conda packaging as default component in OOTs

Please note that all contributions to GNU Radio are considered to be released under the Creative Commons Attribution-ShareAlike (see GNU Radio:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)