Documentation is of paramount importance for users, developers, testers, software architects and students. We use Doxygen, a tool for writing software reference documentation. The documentation is written within the C++ code, in form of comments, and is thus relatively easy to generate (since it can be written along with the source code) and keep up to date. Doxygen scans the code, extracts the documentation and dumps it in HTML, LATEX, RTF or XML formats, cross-referencing documentation and code, so that the reader of a document can easily refer to the actual code. It also automatically generates dependency graphs, inheritance diagrams, and collaboration diagrams.
See the building guide for instructions about of to generate documentation with Doxygen.
-
ProjectProject description, motivation and phylosophy.
-
ProjectGetting the big picture.
-
SoftwareA discussion on the receiver's software architecture.
-
How toBrief description about the internal processes going on when the receiver is running.
-
How to, Software, Source CodeInstructions for building the source code
-
Source CodeProgramming guidelines and code conventions
-
How to, Source CodeInstructions for adding your own processing blocks
-
Project, Source CodeHow to generate documentation from the source code.
-
TestingTesting as a developing methodology
-
How toGuidelines for contributing, sending patches, and so on.
-
GSoCThis page contains guidelines and a list of ideas for participation in Google Summer of Code 2013 program.
-
How to, Source CodeHow to measure software performace and identify bottlenecks.
-
How to, SourceForgeRules and good practices when spotting errors in the source code.
-
How to, Source CodeHow to observe the internals of the software receiver.
-
Hardware, How toHow to use the SiGe GN3S Sampler v2 as RF front-end for GNSS-SDR
-
Hardware, How toHow to use a cheap DVB-T USB dongle as a RF front-end for navigation
-
Papers, ProjectList of academic papers involving GNSS-SDR.
