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
Hello Holger,
Am 24.07.21 um 14:51 schrieb Holger Vogt:
> Carsten,
>
> library versioning: not yet.
>
> Did some experiments with libtool library versioning.
> The input 0:1:0 (code change but no api change) created a
> libngspice.so.0.0.1.
that's correct, just increase the revision (or age if
Carsten,
library versioning: not yet.
Did some experiments with libtool library versioning.
The input 0:1:0 (code change but no api change) created a
libngspice.so.0.0.1.
My Linux Eeschema (5.1.10 from SUSE Leap 15.3 Electronics repository
with ngspice-14) failed immediately because it wants
Master is sufficient, no tarball needed for me! Thanks!
On Thu, Jul 22, 2021, 1:47 PM Holger Vogt wrote:
> Adam,
>
> this is indeed a great idea.
>
> The current ngspice master branch is up-to-date.
>
> https://sourceforge.net/p/ngspice/ngspice/ci/master/tree/
>
> There is also an (automaticall
Hello Holger,
Am 22.07.21 um 21:17 schrieb Holger Vogt:
> With ngspice-35, there will be to changes concerning the
> sharedspice.h API header.
>
> There is now a preprocessor flag definition added
> #define NGSPICE_PACKAGE_VERSION "35"
this means too there is now a proper versioned library built?
With ngspice-35, there will be to changes concerning the
sharedspice.h API header.
There is now a preprocessor flag definition added
#define NGSPICE_PACKAGE_VERSION "35"
All boolean return values are typedefed to 'int'. They
always have been of integer type, but defined in an
old spice tradtion
Adam,
this is indeed a great idea.
The current ngspice master branch is up-to-date.
https://sourceforge.net/p/ngspice/ngspice/ci/master/tree/
There is also an (automatically generated) tarball available
(see the 'Dowmload Snapshot' button from the git web page).
I could also prepare a tarball
Wonderful! I can start building test builds against a development branch
if that's something that's available.
Adam
On Thu, Jul 22, 2021, 8:56 AM Holger Vogt wrote:
> Well so let's wait until ngspice-35 is out (2 weeks?). The config.h bug
> should be removed.
>
>
>
Well so let's wait until ngspice-35 is out (2 weeks?). The config.h bug
should be removed.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-develope
Hi Holger,
Last time Adam and I looked at this, I could not build ngspice-34 and
kicad-nightly on macOS because of the issue with config.h changing.
I have not tried recently; Adam, have you?
-Jon
On Wed, Jul 21, 2021 at 11:14 AM Holger Vogt wrote:
> The nightly for macOS from July 20th is de
The nightly for macOS from July 20th is delivered with ngspice-31.
(https://kicad-downloads.s3.cern.ch/osx/nightly/kicad-unified-20210720-030631-75190370dd.dmg)
This ngspice version is fairly outdated, ngspice-34 is the current
version (with several improvements in the Eeschema/ngspice cooperat
11 matches
Mail list logo
