On Sun, Nov 8, 2026, at 05:24, Thomas Dettbarn wrote:
> UNFORTUNATELY, this means that I would have to create 7 new ports. But
> I am not 100% sure that they would have merits outside of being a build
> dependency.
>
> So my question to you is:
>
> - Should I do it?
> - Should I give them plain names such as cad/trellis and cad/icestorm?
> - Would it be justified to group them in a new subdirectory below cad?
> - Is there a way I have not thought about yet?
Is nextpnr only ever linked to one of these libraries, or is it more akin to
pluggable modules? Are they generally linked statically or dynamically?
My first instinct would be to bundle them in as part of nextpnr, and look at
splitting them out if it turns out that another program can make use of them.
But that depends on whether they're hard linked or pluggable. An alternative
would be to have variants of nextpnr - one for each library, and named
accordingly, with the library bundled in.
Bear in mind that this is just me spitballing on possibilities; I'm nothing
more than a volunteer who joined the mailing list to try to help get Kea up to
date, and have no authority to make any decisions of this sort.
Cheers.
