[Cryptech Tech] novena build instructions

[Olof Kindgren]

On Tue, Aug 18, 2015 at 4:46 PM, Rob Austein <sra at hactrn.net> wrote:
> Interesting.  FuseSoC's GPL3 license would be a problem if we were to
> ship FuseSoC itself, but I don't think it's a problem for a build
> tool.  Will take a closer look next time I'm working on release
> engineering, unless Paul (or somebody) beats me to it.  Thanks!

As you say, the GPLv3 license would only be applicable if you ship
FuseSoC itself (out of curiousity, why would shipping a GPLv3 tool be
a problem?). The generated files shouldn't be covered by that. One of
the core design principles of FuseSoC is that you should be able to
just use it for the parts of the design flow that you want. So when
you build for an FPGA target, all project files and HDL files are
copied to a separate directory, so that you can use them stand-alone
without having to depend on FuseSoC. So one way to use FuseSoC for
release managment is to just let FuseSoC generate the necessary files
and ship that.

As a side note, I see that you have been talking earlier on this list
about Google's ProjectVault. They used FuseSoC for the OpenRISC-based
prototype, so you can hook up the cores from their repo as well quite
easily if you wanted to try them out

Let me know if you need any assistance. Happy to help out

//Olof