Davide Asnaghi
Davide Asnaghi
it would be awesome to merge this ❤️
I actually did not, sorry I did not see this comment, I'll make sure I try to fix it. @markd666 do you have a simple example I can use to...
Ok, I have a PR to address this issue, I will merge it only if it is still relevant: #24
Closed by #24
@mawildoer, seems like the build now just removes all custom footprints from the layout file, so not fixed for us yet. But now the updated files are correct, definitely a...
I take this back, if I add some generics, the project can actually build and modify the layout, but providing custom footprints is still not working and the picker defaults...
This branch is great and I would love to see this functionality merged into main, anything I can do to help here?
Hey @iopapamanoglou, maybe this is a different issue, but with `ato` v0.2.0 you could place a `.step` or `.wrl` model in the `footprints` directory and `ato build` would copy this...
I think this was the PR that introduce the behavior we relied upon https://github.com/atopile/atopile/pull/282
Yeah this is somewhat confusing. My preference would be to use the C++ actions. this should mirror what g++ does under the hood.