You can in fact replace the icons. We just don't support it in the UI.
You just need to replace images.tar.gz, for example on Windows that's
located in C:\Program Files\KiCad\\share\kicad\resources
On Wednesday, September 14, 2022 at 9:38:00 PM UTC-4 Kevin Cozens wrote:
> On 2022-09-14 11:35,
> . There's a lot of zombie code being carried in the Kicad repo for
unclear gain
Welcome to the world of stuff that works and is low hanging fruit for a
bunch of people doing this out of their personal free time.
(Heck honestly at work, we wouldn't bother wasting our paid labor on
"zombie code"
Not sure why you are hijacking this thread.
But you must be on the supported list of ubuntu distros to get v7 (ubuntu
20 and newer) and only 64-bit x86 processors.
https://launchpad.net/~kicad/+archive/ubuntu/kicad-7.0-releases
Space Navigator/Space Mouse support does not exist on Linux and is
This is far out of scope for what KiCad is intended for and would
quickly be broken many times over as we don't have manpower or
interest to maintain it.
It's a lot more work than you make it seem to get it correct and
there'll be demands to add more and more.
Maybe 10 years from now when the
Try now
On Fri, Mar 31, 2023 at 10:08 AM Salvador Tropea
wrote:
> Sorry to insist, the recipe used to create the nightly builds seems to be
> severely broken.
> Last commits on this recipe are from Seth Hillbrand and Jean-Samuel
> Reynaud.
> Can anyone confirm it? No python plugin can be run
https://gitlab.com/kicad/code/kicad/-/issues/2324
https://gitlab.com/kicad/code/kicad/-/issues/2329
It'll require a proposal on file format changes to store those
constraints and overall behavior.
But I don't think anyone would be against it
On Thu, Apr 13, 2023 at 9:41 AM Filip Pešula wrote:
>
We aren't using Metal at all, for now.
>KiCAD is not a SW that demands high CPU power
Computational geometry is actually quite demanding of CPU power as board
complexity increases, so your statement is completely false.
However for simple designs yes, it isn't a real needed.
Most of your slow
Changes need to be tested on Windows arm64 too btw :P
(We have arm64 windows nightlies and 8.0 will see stable arm64 windows
builds)
Libcontext was an awkward hack to get around the disaster of boost::context
making major API changes that didn't match between every distro/platform
for years
You just have to email the list along with what language you are
interested in translating. The language has to be added manually to
weblate by a developer.
Also the language will not appear in KiCad until a good portion is translated.
On Wed, May 10, 2023 at 10:12 PM La_niko wrote:
>
> hi I
Christoph,
Can you alter the build to use the clang linker flag "-flat_namespace" and
see if it works?
Regards,
Mark
On Tue, May 16, 2023, 2:57 PM Christoph Moench-Tegeder
wrote:
> ## Jon Evans (j...@craftyjon.com):
>
> > I don't know what you mean by "major problems" so I can't comment on
We are moving towards some unit tests to validate the plot output.
Such a test already exists for schematic plot output as a kicad-cli
test and will be expanded to PCB eventually.
But, even the recent changes such as
d5bd1f5aea042a238345171b99a195da9e0eab9e were entirely intentional and
not an
I fixed up the kicad cmakelist to be correct. The ccache and distcc logic
was pretty old and dated.
You just need to have ccache on your PATH and you should not need any of
your custom changes in theory now besides setting USE_CCACHE.
On Tue, May 7, 2024 at 3:30 AM Liang Jia wrote:
> Hi All,
>
You were trying to use libeval which lived in `common` inside common.cpp
which lives in `kicommon`
`common` -> static library, depends on kicommon
`kicommon` -> shared library, cannot depend on common
So that's just invalid. Yea theres two libraries, they are slowly being
moved to kicommon as
> So my question is: is the footprint assignment
> BEFORE netlist export to PCB a "design feature", or is it implemented
> this way because of some legacy code from the past? (the question
> originates from pondering of multiboard/multi-pcb-variant design options)
It is an intended design
GitLab, like any other platform, has been suffering from cryptocurrency
abuse which has been resulting in more and more lock down of signups.
There's a new bull wave in crypto so of course the abuse has ramped up.
However, I just confirmed that the phone number verification is risk
assessment
15 matches
Mail list logo