Holger,
You should use something like NGSPICE_PACKAGE_VERSION to avoid namespace
clashes with other header version definitions. PACKAGE_VERSION seems
like it could be an issue.
Cheers,
Wayne
On 2/4/21 3:38 PM, Holger Vogt wrote:
> I prefer adding
> #define PACKAGE_VERSION "34+"
> to
I prefer adding
#define PACKAGE_VERSION "34+"
to sharedspice.h.
sharespice.h has been and will always be there.
In old ngspice releases PACKAGE_VERSION is not defined. But config.h is
there, containing its PACKAGE_VERSION. In ngspice-34 unfortunately
PACKAGE_VERSION will not be available. But
The problem with a new header though is we will need to add yet another
build flag to kicad that a user will have to setbecause we can't
guarantee all platforms will have ngspice > 35 or whateveto look for a new
"version.h"
On Wed, Feb 3, 2021 at 7:04 AM jp charras wrote:
>
> Le 03/02/2021
Le 03/02/2021 à 11:38, Carsten Schoenert a écrit :
Hello Holger,
Am 03.02.21 um 11:20 schrieb Holger Vogt:
I remember some time ago I tried to address the libtool versioning, but
I did not understand it, so abandoned it again.
libtool isn't really easy, yes, but the more complicated thing is
4 matches
Mail list logo
