@Brian, I think your back-annotation tool would be a useful tool for users. As Jon mentioned. Please keep in mind back annotation for pin and gate swapping in being planned for v6. I'm sure this will dovetail in with the work that you are doing so it is important to communicate with the development team what you are working on to prevent duplication of effort and merge conflicts. I cannot stress this enough. We have had too many developers write large pieces of code that could not be used because it didn't fit into what other developers were working on. That is why we have a road map. You should look there first. As always, if you are not sure, ask. As for msys2 build issues. I was incorrect about oce and ngspice not being packaged. They actually are packaged and can be installed using pacman. Will try to do a better job of keeping the windows build instructions up to date. FYI, there is a known issue (see the link Jon provided) in 32-bit builds so I recommend you use 64-bit (x86_64) builds of kicad or you will have to fix a broken path in some of the build.make files in your kicad binary path. Since it sounds like you are going to be hacking on kicad, I would avoid building and installing a binary package. There is no need to install the libraries and docs everytime you want to make a change and rebuild kicad. Building kicad itself takes long enough on windows. The overhead of the libraries will make this process really painful. Cheers, Wayne On 3/7/2018 11:05 AM, Brian Piccioni wrote: > Wayne > > (For some reason your reply is not on the bug website) > > I don't know how to hack the build process to remove the offending > issues. If I did I would have posted a fix rather than a bug. > > My plan is this: I wrote a c-utility RenumKiCadPCB which provides > geographic renumbering of the PCB with full back-annotation to the > schematics and netlist. It recurses the schematic hierarchy completely. > Other applications I tried prior to writing Renum either flat out > failed, only worked in simple cases (i.e. no hierarchy), or had other > major issues. > > I wrote this for me, posted it online, and have received positive > feedback from its users. Because it was written as a command line > program its user base is probably much less than would otherwise have > been the case. > > Since this function is absent from PCBNew (though present in every other > PCB CAD tool I've used) I thought it would make a good addition to the > code base. > > I am pretty sure somebody who knows their way around KiCad could easily > incorporate it into PCBNew so I proposed it and got no takers. I was > also informed the feature set was already frozen (even though the most > recent nightly build changed the menu bar on me). > > So, I figure if I can build KiCad I can: > 1) learn something about a complex project; > 2) learn more about c++; > 3) learn how a gui is coded; > 4) if I am lucky, follow the instructions here http://docs.kicad-pcb.org/doxygen/md_Documentation_development_tool-framework.html#tutorial which will allow me to make a version of PCBNew with Renum built in. > > If I accomplish 3 then perhaps it would be easier to the devs to > consider incorporate this missing function into PCBNew in the future. > > If nothing else I would have learned something. > > Regardless, there is no point in having documentation which provides > step by step build instructions if those instructions fail. > > > Brian > > -----Original Message----- > From: