| ID: | 5701 |
| From: | rn...@igor2.repo.hu |
| Date: | Sat, 18 Jun 2022 19:53:39 +0200 (CEST) |
| Subject: | Re: [pcb-rnd] RFC: project file considerations |
| in-reply-to: | 5700 from ka...@aspodata.se |
On Sat, 18 Jun 2022, karl@aspodata.se wrote: >Regarding: > http://repo.hu/cgi-bin/pool.cgi?project=sch-rnd-aux&cmd=show&node=prj_corners > >under "Assumptions and generic problems" > >"In fact this happens in gschem too, it's just a bit hidden there: > if you don't want to break your multi-sheet design, you always need > to pass all sheet files to gnetlist. Running gnetlist on less sheets > or on just one sheet will yield the wrong netlist." > >This is not true, I have been using hiearchical designs for years >and only needed to specify the top file. I was writing about flat multi-sheet, non-hierarchic design. (That's what multi-sheet means unless we explicitly say hierarchic, as far as I understand). <snip> >Also, regarding "projects", there is metrics and procedures on how >to share projects with other people. You (Igor2) have mentioned it >earlier, but it might make sense to somehow include that into >the "project" nodes somewhere. In sch-rnd this doesn't require special documentation or procedure: you just puck up your sheet files and project file and it will work on any system, since we do not have external file references for symbols. You do not need to pack symbols files, you do not need to ensure library configuration, etc. Regards, Igor2
Reply subtree:
5701 Re: [pcb-rnd] RFC: project file considerations from rn...@igor2.repo.hu