Mail Archives: geda-user/2018/01/29/09:35:52
John:
> What's your favorite makefile rule for an output that comes from several input files?
What do you mean,
. several .sch files not directly related to each other
. or a .sch file with subschematics ?
> Here's my drc, bom, and netlist rules for single page schematics:
Can't help you with drc and netlist for the moment.
> =================drc, bom, and netlist rules=========================
> drc: $(DRC)
>
> $(DRC): %.drc: %.sch
>
> gnetlist -g drc2 $< -o $@
>
>
> bom: $(BOMS)
>
> $(BOMS): %.bom.tsv: %.sch
> gnetlist -g partslist3 $< -o $@
>
>
> net: $(NETS) $(BOMS) $(DRC)
>
> $(NETS): %.net: %.sch
>
> gnetlist -g PCB $< -o $@
> =================drc, bom, and netlist rules=========================
>
> So, if you make a specific rule for a two pager schematic, is there a way to not create the
> outputs for its single pages?
>
> Here's a script I run by hand for the multipage schematic:
>
> #!/bin/bash
> gnetlist -g partslist3 pyflex_f401.sch pyflex_f401_boost.sch -o pyflex_f401_all.net
I use:
%.sch.list: %.sch
GnetParts.pl $<
where GnetParts.pl is
http://aspodata.se/git/openhw/bin/GnetParts.pl
wich uses gnetlist -g partslist1, it fixes the output of gnetlist to
something I can easilier digest, example output in
http://aspodata.se/tmp/gEDA/ *.list1 and list2
But my guess is that it isn't what you're asking about.
What about having a top .sch which with the pages you want included as
subpages and running gnetlist on that, then you will always run your
thing on "single" pages...
Regards,
/Karl Hammar
-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57
- Raw text -