Hi Tom, Can the hyperlink export test not exist in the existing qa_pcbnew test? The code is all in pcbnew's library, so why not just mirror the source layout and put your test as "qa/pcbnew/exporters/test_export_hyperlynx.cpp"?
Otherwise we will eventually have dozens and dozens of tiny unit test executables all in need of CMake files and linking. OTOH, if the hyperlynx stuff was a separate library, then it would make sense to have a separate test exec. At that point, we'd presumably have shared libs anyway. Cheers, John On Fri, Apr 5, 2019 at 1:16 AM Tomasz Wlostowski <tomasz.wlostow...@cern.ch> wrote: > > Hi, > > We needed to do some signal/power integrity simulations on one of our > Kicad designs and in order to do that, we needed to convert a Kicad PCB > to Hyperlynx format. Luckily, the format is simple, all text and well > documented in [1], so here comes a patch that adds a Hyperlynx exporter. > > Notes: > - since Kicad doesn't have a concept of board stackup (permittivities, > loss tangent, dielectric types, etc.), the exporter writes a dummy > stackup. Edit it to match the PCB spec in Hyperlynx. > - no support for offset pad holes, slotted pad holes, > trapezoid/polygonal pads (it seems HL format doesn't support such > features or I need to figure out how to emulate them). > - no support for thermal pads (yet) > - no error reporting. > > Looking forward to your feedback & wish you happy testing, > Tom > > [1] http://www.ibis.org/birds/bird33.txt > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
