On Thu, Sep 19, 2013 at 10:45 AM, Tim [email protected] wrote:
all the recipes they will be building.
At the end of the day we do have a choice now between trying to keep build
configurations fairly static and simple (defined only by their recipe set
and guaranteed for repeatability - which is great for performing repeatable
testing, versioning, and packaging) or allowing it to become a monolithic
thing that has lots of different user prompted states and options. It’s
not clear that we can’t achieve both - but we would sacrifice a bit of
conciseness and recipe simplicity to get there
At the least, we’ll want to get a recipe for Doxygen, which is going
to entail a large number of dependencies, too, so it might take some
time to get all of those recipes right. At that point, it should be
easy enough to just edit gnuradio.lwr to turn on Doxygen for those who
really want it.
Also, remember that we host the documentation online, including many
of the past versions, the most recent released version, and the
current master updated weekly:
And one of the GSoC projects going on this year was to make some
improvements to GRC, including access to the online manual
documentation for given blocks, so requiring them to be built locally
might not be as important once we get this work rolled in.