At this point, KiCad isn't defining a version requirement on ngspice, so
any way you choose to do it would work for us.
As for the issue compiling earlier, did you try to use your new ngspice
build with a pre-built KiCad version or did you build that KiCad version
yourself?
-Ian
On Tue, Jul 27,
Am 27.07.21 um 20:12 schrieb Holger Vogt:
> Carsten,
>
> it is not about what I should do, but what the KiCad devs should do to
> allow me adding versioning to shared ngspice. I will add versioning if
> it is aknowledged by KiCad/Eeschema.
That's not the question in my eyes. It's not something
Carsten,
it is not about what I should do, but what the KiCad devs should do to
allow me adding versioning to shared ngspice. I will add versioning if
it is aknowledged by KiCad/Eeschema.
Holger
___
Mailing list: https://launchpad.net/~kicad-deve
Hello Holger,
Am 27.07.21 um 14:03 schrieb Holger Vogt:
> So what would be the correct action?
>
> When I compile ngspice, I get (besides libngspice.so.0.0.0 or
> libngspice.so.0.0.1) two aliases libngspice.so.0 and libngspice.so. What
> would be the correct version to link to?
there is nothin
So what would be the correct action?
When I compile ngspice, I get (besides libngspice.so.0.0.0 or
libngspice.so.0.0.1) two aliases libngspice.so.0 and libngspice.so. What
would be the correct version to link to?
___
Mailing list: https://launchpa
5 matches
Mail list logo
