Re: [Kicad-developers] ngspice-34

[Holger Vogt]

Probably by end of June ngspice-35 will be available.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Adam Wolf]

Just curious, what sort of timeframe would we be looking at for 35?

Adam Wolf

On Wed, Apr 28, 2021 at 5:59 AM Nick Østergaard  wrote:
>
> Ok, thank you. I will follow-up with archlinux packager for ngspice.
>
> On Wed, 28 Apr 2021 at 10:02, Holger Vogt  wrote:
>>
>> config.h for ngspice should not be distributed, because it is a local,
>> OS dependent autogenerated file, and might interfere with other packages.
>>
>> So I did remove it in ngspice-34.
>>
>> Nevertheless KiCad uses it (from its position in
>> /usr/include/ngspice/config.h) to extract compile time version info for
>> ngspice.
>>
>> Due to a bug from my side config.h was still distributed with
>> ngspice-34, now located in /usr/include/config.h.
>>
>> ngspice-35 will contain version info in sharedspice.h (which is always
>> distributed), and there are some suggestion by Carsten how to handle the
>> version info issue "the correct way" (unfortunately barely Windows
>> compatible).
>>
>> So indeed an intermediate sultion for ngspice-34 might be to shift
>> config.h to /usr/include/ngspice/config.h before compilation.
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Nick Østergaard]

Ok, thank you. I will follow-up with archlinux packager for ngspice.

On Wed, 28 Apr 2021 at 10:02, Holger Vogt  wrote:

> config.h for ngspice should not be distributed, because it is a local,
> OS dependent autogenerated file, and might interfere with other packages.
>
> So I did remove it in ngspice-34.
>
> Nevertheless KiCad uses it (from its position in
> /usr/include/ngspice/config.h) to extract compile time version info for
> ngspice.
>
> Due to a bug from my side config.h was still distributed with
> ngspice-34, now located in /usr/include/config.h.
>
> ngspice-35 will contain version info in sharedspice.h (which is always
> distributed), and there are some suggestion by Carsten how to handle the
> version info issue "the correct way" (unfortunately barely Windows
> compatible).
>
> So indeed an intermediate sultion for ngspice-34 might be to shift
> config.h to /usr/include/ngspice/config.h before compilation.
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Holger Vogt]

config.h for ngspice should not be distributed, because it is a local, 
OS dependent autogenerated file, and might interfere with other packages.


So I did remove it in ngspice-34.

Nevertheless KiCad uses it (from its position in 
/usr/include/ngspice/config.h) to extract compile time version info for 
ngspice.


Due to a bug from my side config.h was still distributed with 
ngspice-34, now located in /usr/include/config.h.


ngspice-35 will contain version info in sharedspice.h (which is always 
distributed), and there are some suggestion by Carsten how to handle the 
version info issue "the correct way" (unfortunately barely Windows 
compatible).


So indeed an intermediate sultion for ngspice-34 might be to shift 
config.h to /usr/include/ngspice/config.h before compilation.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Nick Østergaard]

Hi

What is the solution to this issue. I just hit issues with ngspice-34 in
archlinux. [1]

There is a /usr/include/config.h

Should this be put in /usr/include/ngspice/config.h?

I lost track of this discussion, so I am not really sure what happened and
why. Just slightly surprised that it appears broken somehow.

Regards
Nick

[1] https://aur.archlinux.org/packages/kicad-git/#comment-804217

On Tue, 23 Mar 2021 at 15:22, Holger Vogt  wrote:

> The intention is to not at all install config.h.
>
> Installing it into ./include was a bug in ngspice-34 which has already
> been removed in the current ngspice master branch.
>
> Perhaps you may make use of this bug by automatically moving config.h
> from <...>/include/ to <...>/include/ngspice/ when building KiCad,
> before we will have a solution without config.h in ngspice-35?
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Wayne Stambaugh]

I guess that's not going to work.  We may just have to punt on a
sensible solution. :(

On 3/23/21 6:03 PM, Mark Roszko wrote:
> pkgconfig is only available for builds within vcpkg for builds of libraries.
> 
> kicad does not build within vcpkg, it builds outside vcpkg using vcpkg.
> This is the intended mode of use for applications.
> 
> On Tue, Mar 23, 2021 at 12:09 PM Wayne Stambaugh  > wrote:
> 
> Did I misunderstand Marks's comments about MSVC?  I though he said that
> pkg-config would not be available to KiCad at runtime and that it would
> be available (I'm assuming via vcpkg) at build time.  I really want to
> avoid a separate solution for MSVC if possible.
> 
> On 3/23/21 11:32 AM, Jon Evans wrote:
> > As Wayne points out, compatibility with older ngspice versions
> needs to
> > be considered, as well as Windows/vcpkg.
> >
> > Since pkg-config apparently can't be used in the MSVC/vcpkg
> environment
> > during the kicad build, the only option I can think of is to
> generate a
> > version header as part of the ngspice vcpkg port itself.
> >
> > So, there would be two different paths, one for Windows/MSVC and
> one for
> > other platforms.
> >
> > -Jon
> >
> > On Tue, Mar 23, 2021 at 11:28 AM Jonatan Liljedahl
> mailto:li...@kymatica.com>
> > >> wrote:
> >
> >     Ah, yes that sounds reasonable. I guess
> >     /CMakeModules/Findngspice.cmake could be modified to use
> pkg-config to
> >     get the version and paths needed?
> >
> >     On Tue, Mar 23, 2021 at 4:20 PM Jon Evans  
> >     >> wrote:
> >     >
> >     > It sounds like the preference is to move away from using a
> >     config.h at all, which means all the KiCad packaging systems would
> >     need to update to use pkg-config to generate a header which
> can then
> >     be included in kicad's build process.  Is that correct?
> >     >
> >     > On Tue, Mar 23, 2021 at 11:15 AM Jonatan Liljedahl
> >     mailto:li...@kymatica.com>
> >> wrote:
> >     >>
> >     >> If ngspice-35 is not ready to be tagged soon, perhaps
> Holger could
> >     >> make a branch called "ngspice-34-config-fix" or something,
> based on
> >     >> the ngspice-34 tag but only adding the simple fix of installing
> >     >> config.h into /include/ngspice/ instead? Then KiCad
> packagers could
> >     >> build from this branch? Unless some packages are not using
> locally
> >     >> built ngspice? Just some ideas of possible solutions...
> >     >>
> >     >> Cheers
> >     >>
> >     >> On Tue, Mar 23, 2021 at 3:22 PM Holger Vogt
> >     mailto:holger.v...@uni-due.de>
> >> wrote:
> >     >> >
> >     >> > The intention is to not at all install config.h.
> >     >> >
> >     >> > Installing it into ./include was a bug in ngspice-34
> which has
> >     already
> >     >> > been removed in the current ngspice master branch.
> >     >> >
> >     >> > Perhaps you may make use of this bug by automatically moving
> >     config.h
> >     >> > from <...>/include/ to <...>/include/ngspice/ when
> building KiCad,
> >     >> > before we will have a solution without config.h in
> ngspice-35?
> >     >> >
> >     >> >
> >     >> > ___
> >     >> > Mailing list: https://launchpad.net/~kicad-developers
> 
> >      >
> >     >> > Post to     : kicad-developers@lists.launchpad.net
> 
> >      >
> >     >> > Unsubscribe : https://launchpad.net/~kicad-developers
> 
> >      >
> >     >> > More help   : https://help.launchpad.net/ListHelp
> 
> >      >
> >     >>
> >     >>
> >     >>
> >     >> --
> >     >> /Jonatan
> >     >> http://kymatica.com 
> >
> >     >>
> >     >> ___
> >     >> Mailing list: https://launchpad.net/~kicad-developers
> 

Re: [Kicad-developers] ngspice-34

[Wayne Stambaugh]

I guess that's not going to work.  We may just have to punt on a
sensible solution. :(

On 3/23/21 6:03 PM, Mark Roszko wrote:
> pkgconfig is only available for builds within vcpkg for builds of libraries.
> 
> kicad does not build within vcpkg, it builds outside vcpkg using vcpkg.
> This is the intended mode of use for applications.
> 
> On Tue, Mar 23, 2021 at 12:09 PM Wayne Stambaugh  > wrote:
> 
> Did I misunderstand Marks's comments about MSVC?  I though he said that
> pkg-config would not be available to KiCad at runtime and that it would
> be available (I'm assuming via vcpkg) at build time.  I really want to
> avoid a separate solution for MSVC if possible.
> 
> On 3/23/21 11:32 AM, Jon Evans wrote:
> > As Wayne points out, compatibility with older ngspice versions
> needs to
> > be considered, as well as Windows/vcpkg.
> >
> > Since pkg-config apparently can't be used in the MSVC/vcpkg
> environment
> > during the kicad build, the only option I can think of is to
> generate a
> > version header as part of the ngspice vcpkg port itself.
> >
> > So, there would be two different paths, one for Windows/MSVC and
> one for
> > other platforms.
> >
> > -Jon
> >
> > On Tue, Mar 23, 2021 at 11:28 AM Jonatan Liljedahl
> mailto:li...@kymatica.com>
> > >> wrote:
> >
> >     Ah, yes that sounds reasonable. I guess
> >     /CMakeModules/Findngspice.cmake could be modified to use
> pkg-config to
> >     get the version and paths needed?
> >
> >     On Tue, Mar 23, 2021 at 4:20 PM Jon Evans  
> >     >> wrote:
> >     >
> >     > It sounds like the preference is to move away from using a
> >     config.h at all, which means all the KiCad packaging systems would
> >     need to update to use pkg-config to generate a header which
> can then
> >     be included in kicad's build process.  Is that correct?
> >     >
> >     > On Tue, Mar 23, 2021 at 11:15 AM Jonatan Liljedahl
> >     mailto:li...@kymatica.com>
> >> wrote:
> >     >>
> >     >> If ngspice-35 is not ready to be tagged soon, perhaps
> Holger could
> >     >> make a branch called "ngspice-34-config-fix" or something,
> based on
> >     >> the ngspice-34 tag but only adding the simple fix of installing
> >     >> config.h into /include/ngspice/ instead? Then KiCad
> packagers could
> >     >> build from this branch? Unless some packages are not using
> locally
> >     >> built ngspice? Just some ideas of possible solutions...
> >     >>
> >     >> Cheers
> >     >>
> >     >> On Tue, Mar 23, 2021 at 3:22 PM Holger Vogt
> >     mailto:holger.v...@uni-due.de>
> >> wrote:
> >     >> >
> >     >> > The intention is to not at all install config.h.
> >     >> >
> >     >> > Installing it into ./include was a bug in ngspice-34
> which has
> >     already
> >     >> > been removed in the current ngspice master branch.
> >     >> >
> >     >> > Perhaps you may make use of this bug by automatically moving
> >     config.h
> >     >> > from <...>/include/ to <...>/include/ngspice/ when
> building KiCad,
> >     >> > before we will have a solution without config.h in
> ngspice-35?
> >     >> >
> >     >> >
> >     >> > ___
> >     >> > Mailing list: https://launchpad.net/~kicad-developers
> 
> >      >
> >     >> > Post to     : kicad-developers@lists.launchpad.net
> 
> >      >
> >     >> > Unsubscribe : https://launchpad.net/~kicad-developers
> 
> >      >
> >     >> > More help   : https://help.launchpad.net/ListHelp
> 
> >      >
> >     >>
> >     >>
> >     >>
> >     >> --
> >     >> /Jonatan
> >     >> http://kymatica.com 
> >
> >     >>
> >     >> ___
> >     >> Mailing list: https://launchpad.net/~kicad-developers
> 

Re: [Kicad-developers] ngspice-34

[Mark Roszko]

pkgconfig is only available for builds within vcpkg for builds of libraries.

kicad does not build within vcpkg, it builds outside vcpkg using vcpkg.
This is the intended mode of use for applications.

On Tue, Mar 23, 2021 at 12:09 PM Wayne Stambaugh 
wrote:

> Did I misunderstand Marks's comments about MSVC?  I though he said that
> pkg-config would not be available to KiCad at runtime and that it would
> be available (I'm assuming via vcpkg) at build time.  I really want to
> avoid a separate solution for MSVC if possible.
>
> On 3/23/21 11:32 AM, Jon Evans wrote:
> > As Wayne points out, compatibility with older ngspice versions needs to
> > be considered, as well as Windows/vcpkg.
> >
> > Since pkg-config apparently can't be used in the MSVC/vcpkg environment
> > during the kicad build, the only option I can think of is to generate a
> > version header as part of the ngspice vcpkg port itself.
> >
> > So, there would be two different paths, one for Windows/MSVC and one for
> > other platforms.
> >
> > -Jon
> >
> > On Tue, Mar 23, 2021 at 11:28 AM Jonatan Liljedahl  > > wrote:
> >
> > Ah, yes that sounds reasonable. I guess
> > /CMakeModules/Findngspice.cmake could be modified to use pkg-config
> to
> > get the version and paths needed?
> >
> > On Tue, Mar 23, 2021 at 4:20 PM Jon Evans  > > wrote:
> > >
> > > It sounds like the preference is to move away from using a
> > config.h at all, which means all the KiCad packaging systems would
> > need to update to use pkg-config to generate a header which can then
> > be included in kicad's build process.  Is that correct?
> > >
> > > On Tue, Mar 23, 2021 at 11:15 AM Jonatan Liljedahl
> > mailto:li...@kymatica.com>> wrote:
> > >>
> > >> If ngspice-35 is not ready to be tagged soon, perhaps Holger could
> > >> make a branch called "ngspice-34-config-fix" or something, based
> on
> > >> the ngspice-34 tag but only adding the simple fix of installing
> > >> config.h into /include/ngspice/ instead? Then KiCad packagers
> could
> > >> build from this branch? Unless some packages are not using locally
> > >> built ngspice? Just some ideas of possible solutions...
> > >>
> > >> Cheers
> > >>
> > >> On Tue, Mar 23, 2021 at 3:22 PM Holger Vogt
> > mailto:holger.v...@uni-due.de>> wrote:
> > >> >
> > >> > The intention is to not at all install config.h.
> > >> >
> > >> > Installing it into ./include was a bug in ngspice-34 which has
> > already
> > >> > been removed in the current ngspice master branch.
> > >> >
> > >> > Perhaps you may make use of this bug by automatically moving
> > config.h
> > >> > from <...>/include/ to <...>/include/ngspice/ when building
> KiCad,
> > >> > before we will have a solution without config.h in ngspice-35?
> > >> >
> > >> >
> > >> > ___
> > >> > Mailing list: https://launchpad.net/~kicad-developers
> > 
> > >> > Post to : kicad-developers@lists.launchpad.net
> > 
> > >> > Unsubscribe : https://launchpad.net/~kicad-developers
> > 
> > >> > More help   : https://help.launchpad.net/ListHelp
> > 
> > >>
> > >>
> > >>
> > >> --
> > >> /Jonatan
> > >> http://kymatica.com 
> > >>
> > >> ___
> > >> Mailing list: https://launchpad.net/~kicad-developers
> > 
> > >> Post to : kicad-developers@lists.launchpad.net
> > 
> > >> Unsubscribe : https://launchpad.net/~kicad-developers
> > 
> > >> More help   : https://help.launchpad.net/ListHelp
> > 
> >
> >
> >
> > --
> > /Jonatan
> > http://kymatica.com 
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>


-- 
Mark
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : 

Re: [Kicad-developers] ngspice-34

[Wayne Stambaugh]

Did I misunderstand Marks's comments about MSVC?  I though he said that
pkg-config would not be available to KiCad at runtime and that it would
be available (I'm assuming via vcpkg) at build time.  I really want to
avoid a separate solution for MSVC if possible.

On 3/23/21 11:32 AM, Jon Evans wrote:
> As Wayne points out, compatibility with older ngspice versions needs to
> be considered, as well as Windows/vcpkg.
> 
> Since pkg-config apparently can't be used in the MSVC/vcpkg environment
> during the kicad build, the only option I can think of is to generate a
> version header as part of the ngspice vcpkg port itself.
> 
> So, there would be two different paths, one for Windows/MSVC and one for
> other platforms.
> 
> -Jon
> 
> On Tue, Mar 23, 2021 at 11:28 AM Jonatan Liljedahl  > wrote:
> 
> Ah, yes that sounds reasonable. I guess
> /CMakeModules/Findngspice.cmake could be modified to use pkg-config to
> get the version and paths needed?
> 
> On Tue, Mar 23, 2021 at 4:20 PM Jon Evans  > wrote:
> >
> > It sounds like the preference is to move away from using a
> config.h at all, which means all the KiCad packaging systems would
> need to update to use pkg-config to generate a header which can then
> be included in kicad's build process.  Is that correct?
> >
> > On Tue, Mar 23, 2021 at 11:15 AM Jonatan Liljedahl
> mailto:li...@kymatica.com>> wrote:
> >>
> >> If ngspice-35 is not ready to be tagged soon, perhaps Holger could
> >> make a branch called "ngspice-34-config-fix" or something, based on
> >> the ngspice-34 tag but only adding the simple fix of installing
> >> config.h into /include/ngspice/ instead? Then KiCad packagers could
> >> build from this branch? Unless some packages are not using locally
> >> built ngspice? Just some ideas of possible solutions...
> >>
> >> Cheers
> >>
> >> On Tue, Mar 23, 2021 at 3:22 PM Holger Vogt
> mailto:holger.v...@uni-due.de>> wrote:
> >> >
> >> > The intention is to not at all install config.h.
> >> >
> >> > Installing it into ./include was a bug in ngspice-34 which has
> already
> >> > been removed in the current ngspice master branch.
> >> >
> >> > Perhaps you may make use of this bug by automatically moving
> config.h
> >> > from <...>/include/ to <...>/include/ngspice/ when building KiCad,
> >> > before we will have a solution without config.h in ngspice-35?
> >> >
> >> >
> >> > ___
> >> > Mailing list: https://launchpad.net/~kicad-developers
> 
> >> > Post to     : kicad-developers@lists.launchpad.net
> 
> >> > Unsubscribe : https://launchpad.net/~kicad-developers
> 
> >> > More help   : https://help.launchpad.net/ListHelp
> 
> >>
> >>
> >>
> >> --
> >> /Jonatan
> >> http://kymatica.com 
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> 
> >> Post to     : kicad-developers@lists.launchpad.net
> 
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> >> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> -- 
> /Jonatan
> http://kymatica.com 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Jon Evans]

As Wayne points out, compatibility with older ngspice versions needs to be
considered, as well as Windows/vcpkg.

Since pkg-config apparently can't be used in the MSVC/vcpkg environment
during the kicad build, the only option I can think of is to generate a
version header as part of the ngspice vcpkg port itself.

So, there would be two different paths, one for Windows/MSVC and one for
other platforms.

-Jon

On Tue, Mar 23, 2021 at 11:28 AM Jonatan Liljedahl 
wrote:

> Ah, yes that sounds reasonable. I guess
> /CMakeModules/Findngspice.cmake could be modified to use pkg-config to
> get the version and paths needed?
>
> On Tue, Mar 23, 2021 at 4:20 PM Jon Evans  wrote:
> >
> > It sounds like the preference is to move away from using a config.h at
> all, which means all the KiCad packaging systems would need to update to
> use pkg-config to generate a header which can then be included in kicad's
> build process.  Is that correct?
> >
> > On Tue, Mar 23, 2021 at 11:15 AM Jonatan Liljedahl 
> wrote:
> >>
> >> If ngspice-35 is not ready to be tagged soon, perhaps Holger could
> >> make a branch called "ngspice-34-config-fix" or something, based on
> >> the ngspice-34 tag but only adding the simple fix of installing
> >> config.h into /include/ngspice/ instead? Then KiCad packagers could
> >> build from this branch? Unless some packages are not using locally
> >> built ngspice? Just some ideas of possible solutions...
> >>
> >> Cheers
> >>
> >> On Tue, Mar 23, 2021 at 3:22 PM Holger Vogt 
> wrote:
> >> >
> >> > The intention is to not at all install config.h.
> >> >
> >> > Installing it into ./include was a bug in ngspice-34 which has already
> >> > been removed in the current ngspice master branch.
> >> >
> >> > Perhaps you may make use of this bug by automatically moving config.h
> >> > from <...>/include/ to <...>/include/ngspice/ when building KiCad,
> >> > before we will have a solution without config.h in ngspice-35?
> >> >
> >> >
> >> > ___
> >> > Mailing list: https://launchpad.net/~kicad-developers
> >> > Post to : kicad-developers@lists.launchpad.net
> >> > Unsubscribe : https://launchpad.net/~kicad-developers
> >> > More help   : https://help.launchpad.net/ListHelp
> >>
> >>
> >>
> >> --
> >> /Jonatan
> >> http://kymatica.com
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
>
>
>
> --
> /Jonatan
> http://kymatica.com
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Jonatan Liljedahl]

Ah, yes that sounds reasonable. I guess
/CMakeModules/Findngspice.cmake could be modified to use pkg-config to
get the version and paths needed?

On Tue, Mar 23, 2021 at 4:20 PM Jon Evans  wrote:
>
> It sounds like the preference is to move away from using a config.h at all, 
> which means all the KiCad packaging systems would need to update to use 
> pkg-config to generate a header which can then be included in kicad's build 
> process.  Is that correct?
>
> On Tue, Mar 23, 2021 at 11:15 AM Jonatan Liljedahl  wrote:
>>
>> If ngspice-35 is not ready to be tagged soon, perhaps Holger could
>> make a branch called "ngspice-34-config-fix" or something, based on
>> the ngspice-34 tag but only adding the simple fix of installing
>> config.h into /include/ngspice/ instead? Then KiCad packagers could
>> build from this branch? Unless some packages are not using locally
>> built ngspice? Just some ideas of possible solutions...
>>
>> Cheers
>>
>> On Tue, Mar 23, 2021 at 3:22 PM Holger Vogt  wrote:
>> >
>> > The intention is to not at all install config.h.
>> >
>> > Installing it into ./include was a bug in ngspice-34 which has already
>> > been removed in the current ngspice master branch.
>> >
>> > Perhaps you may make use of this bug by automatically moving config.h
>> > from <...>/include/ to <...>/include/ngspice/ when building KiCad,
>> > before we will have a solution without config.h in ngspice-35?
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> --
>> /Jonatan
>> http://kymatica.com
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp



-- 
/Jonatan
http://kymatica.com

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Wayne Stambaugh]

On 3/23/21 11:20 AM, Jon Evans wrote:
> It sounds like the preference is to move away from using a config.h at
> all, which means all the KiCad packaging systems would need to update to
> use pkg-config to generate a header which can then be included in
> kicad's build process.  Is that correct?

I would say yes assuming ngspice supports pkg-config back to a least
version 32.  This would be a reliable way to address this for most if
not all existing platforms now and going forward assuming ngspice will
continue to support pkg-config.

> 
> On Tue, Mar 23, 2021 at 11:15 AM Jonatan Liljedahl  > wrote:
> 
> If ngspice-35 is not ready to be tagged soon, perhaps Holger could
> make a branch called "ngspice-34-config-fix" or something, based on
> the ngspice-34 tag but only adding the simple fix of installing
> config.h into /include/ngspice/ instead? Then KiCad packagers could
> build from this branch? Unless some packages are not using locally
> built ngspice? Just some ideas of possible solutions...
> 
> Cheers
> 
> On Tue, Mar 23, 2021 at 3:22 PM Holger Vogt  > wrote:
> >
> > The intention is to not at all install config.h.
> >
> > Installing it into ./include was a bug in ngspice-34 which has already
> > been removed in the current ngspice master branch.
> >
> > Perhaps you may make use of this bug by automatically moving config.h
> > from <...>/include/ to <...>/include/ngspice/ when building KiCad,
> > before we will have a solution without config.h in ngspice-35?
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> 
> > Post to     : kicad-developers@lists.launchpad.net
> 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> 
> > More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> -- 
> /Jonatan
> http://kymatica.com 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Jon Evans]

It sounds like the preference is to move away from using a config.h at all,
which means all the KiCad packaging systems would need to update to use
pkg-config to generate a header which can then be included in kicad's build
process.  Is that correct?

On Tue, Mar 23, 2021 at 11:15 AM Jonatan Liljedahl 
wrote:

> If ngspice-35 is not ready to be tagged soon, perhaps Holger could
> make a branch called "ngspice-34-config-fix" or something, based on
> the ngspice-34 tag but only adding the simple fix of installing
> config.h into /include/ngspice/ instead? Then KiCad packagers could
> build from this branch? Unless some packages are not using locally
> built ngspice? Just some ideas of possible solutions...
>
> Cheers
>
> On Tue, Mar 23, 2021 at 3:22 PM Holger Vogt 
> wrote:
> >
> > The intention is to not at all install config.h.
> >
> > Installing it into ./include was a bug in ngspice-34 which has already
> > been removed in the current ngspice master branch.
> >
> > Perhaps you may make use of this bug by automatically moving config.h
> > from <...>/include/ to <...>/include/ngspice/ when building KiCad,
> > before we will have a solution without config.h in ngspice-35?
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
>
>
> --
> /Jonatan
> http://kymatica.com
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Jonatan Liljedahl]

If ngspice-35 is not ready to be tagged soon, perhaps Holger could
make a branch called "ngspice-34-config-fix" or something, based on
the ngspice-34 tag but only adding the simple fix of installing
config.h into /include/ngspice/ instead? Then KiCad packagers could
build from this branch? Unless some packages are not using locally
built ngspice? Just some ideas of possible solutions...

Cheers

On Tue, Mar 23, 2021 at 3:22 PM Holger Vogt  wrote:
>
> The intention is to not at all install config.h.
>
> Installing it into ./include was a bug in ngspice-34 which has already
> been removed in the current ngspice master branch.
>
> Perhaps you may make use of this bug by automatically moving config.h
> from <...>/include/ to <...>/include/ngspice/ when building KiCad,
> before we will have a solution without config.h in ngspice-35?
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp



-- 
/Jonatan
http://kymatica.com

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Holger Vogt]

The intention is to not at all install config.h.

Installing it into ./include was a bug in ngspice-34 which has already 
been removed in the current ngspice master branch.


Perhaps you may make use of this bug by automatically moving config.h 
from <...>/include/ to <...>/include/ngspice/ when building KiCad, 
before we will have a solution without config.h in ngspice-35?



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Jonatan Liljedahl]

I've built KiCad on macOS with ngspice built from the "ngspice-34" git
tag, but there is one problem:

KiCad is looking for /include/ngspice/config.h, but
ngspice installs it in /include/config.h:

./include
./include/config.h
./include/ngspice
./include/ngspice/sharedspice.h
...

So after copying/linking config.h into include/ngspice/ KiCad finds it
and builds as expected.
I can only assume that it's an error in ngspice build system to put
config.h directly in the include directory! Quite high chance that it
would collide with some other package.

Perhaps easier to just wait for ngspice-35 instead of working around it here?

Cheers

On Tue, Mar 23, 2021 at 9:51 AM Holger Vogt  wrote:
>
> sharedspice.h (the only header to be distributed with ngspice) does
> contain something like
>
> #ifndef NGSPICE_PACKAGE_VERSION
> #define NGSPICE_PACKAGE_VERSION "34+"
> #endif
>
> in the ngspice git master branch, and available later in ngspice-35.
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp



-- 
/Jonatan
http://kymatica.com

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Wayne Stambaugh]

On 3/22/21 7:02 PM, Mark Roszko wrote:
>> Does vcpkg support pkg-config?
> 
> vcpkg can use pkg-config for building its own libraries.
> However vcpkg will not share it outside of itself, meaning kicad has no
> ability to use it easily

I wasn't thinking about calling it from KiCad at runtime.  I was
thinking running it from CMake at build time to fetch the ngspice build
version.

> 
> On Mon, Mar 22, 2021 at 3:18 PM Wayne Stambaugh  > wrote:
> 
> Would pkg-config work on all platforms?  I know it works on Linux and
> msys2.  I would rather not have a separate hack for every platform if we
> can avoid it.  Does vcpkg support pkg-config?  If so, then it should be
> possible to use it on msvc builds as well.
> 
> On 3/22/21 2:57 PM, Jon Evans wrote:
> > Bumping this thread as we don't seem to have a resolution yet.
> >
> > The Windows vcpkg package works as there is still a config.h with the
> > version in the "visualc" directory.
> >
> > But, MacOS doesn't build and I guess some Linux distros don't either.
> >
> > Can we make pkg-config work for MacOS?
> >
> > On Wed, Feb 3, 2021 at 1:45 PM Carsten Schoenert
> > mailto:c.schoen...@t-online.de>
> >>
> wrote:
> >
> >     Am 03.02.21 um 13:03 schrieb jp charras:
> >     > OTOH, a version.h file is not a bad idea (read: for me a
> very good
> >     idea):
> >     >
> >     > at least the name is already a useful comment and it request
> only
> >     a very
> >     > few amount of work.
> >     >
> >     > Many tools use this trick (for instance opencascade, and most of
> >     other
> >     > tools we are using in Kicad), and one **big** advantage it works
> >     outside
> >     > the libtool stuff.
> >
> >     For simple things like version detection pkg-config is already
> enough,
> >     no need for mostly incompatible hacks. Even different shells
> on the same
> >     host can behavior really unexpected.
> >
> >     If you need to detect the version of ngspice you will need to
> do this
> >     this already before any build is started.
> >
> >     > $ pkg-config --modversion ngspice
> >     > 33
> >     --
> >     Regards
> >     Carsten
> >
> >     ___
> >     Mailing list: https://launchpad.net/~kicad-developers
> 
> >      >
> >     Post to     : kicad-developers@lists.launchpad.net
> 
> >      >
> >     Unsubscribe : https://launchpad.net/~kicad-developers
> 
> >      >
> >     More help   : https://help.launchpad.net/ListHelp
> 
> >      >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> 
> > Post to     : kicad-developers@lists.launchpad.net
> 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> 
> > More help   : https://help.launchpad.net/ListHelp
> 
> >
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> -- 
> Mark

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Holger Vogt]

Am 23.03.2021 um 00:02 schrieb Mark Roszko:

 > Does vcpkg support pkg-config?

vcpkg can use pkg-config for building its own libraries.
However vcpkg will not share it outside of itself, meaning kicad has no 
ability to use it easily




When making ngspice with MSVC, and if building KiCad wants to use 
pkg-config with ngspice.pc, how to create ngspice.pc from ngspice.pc.in 
in the MSVC environment?


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Holger Vogt]

sharedspice.h (the only header to be distributed with ngspice) does 
contain something like


#ifndef NGSPICE_PACKAGE_VERSION
#define NGSPICE_PACKAGE_VERSION "34+"
#endif

in the ngspice git master branch, and available later in ngspice-35.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Holger Vogt]

pkg-config is ok on macOS, I had to manually add the path to ngspice.pc 
in the env variable PKG_CONFIG_PATH.




Can we make pkg-config work for MacOS?



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Mark Roszko]

> Does vcpkg support pkg-config?

vcpkg can use pkg-config for building its own libraries.
However vcpkg will not share it outside of itself, meaning kicad has no
ability to use it easily

On Mon, Mar 22, 2021 at 3:18 PM Wayne Stambaugh 
wrote:

> Would pkg-config work on all platforms?  I know it works on Linux and
> msys2.  I would rather not have a separate hack for every platform if we
> can avoid it.  Does vcpkg support pkg-config?  If so, then it should be
> possible to use it on msvc builds as well.
>
> On 3/22/21 2:57 PM, Jon Evans wrote:
> > Bumping this thread as we don't seem to have a resolution yet.
> >
> > The Windows vcpkg package works as there is still a config.h with the
> > version in the "visualc" directory.
> >
> > But, MacOS doesn't build and I guess some Linux distros don't either.
> >
> > Can we make pkg-config work for MacOS?
> >
> > On Wed, Feb 3, 2021 at 1:45 PM Carsten Schoenert
> > mailto:c.schoen...@t-online.de>> wrote:
> >
> > Am 03.02.21 um 13:03 schrieb jp charras:
> > > OTOH, a version.h file is not a bad idea (read: for me a very good
> > idea):
> > >
> > > at least the name is already a useful comment and it request only
> > a very
> > > few amount of work.
> > >
> > > Many tools use this trick (for instance opencascade, and most of
> > other
> > > tools we are using in Kicad), and one **big** advantage it works
> > outside
> > > the libtool stuff.
> >
> > For simple things like version detection pkg-config is already
> enough,
> > no need for mostly incompatible hacks. Even different shells on the
> same
> > host can behavior really unexpected.
> >
> > If you need to detect the version of ngspice you will need to do this
> > this already before any build is started.
> >
> > > $ pkg-config --modversion ngspice
> > > 33
> > --
> > Regards
> > Carsten
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > 
> > Post to : kicad-developers@lists.launchpad.net
> > 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > 
> > More help   : https://help.launchpad.net/ListHelp
> > 
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>


-- 
Mark
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Wayne Stambaugh]

Would pkg-config work on all platforms?  I know it works on Linux and
msys2.  I would rather not have a separate hack for every platform if we
can avoid it.  Does vcpkg support pkg-config?  If so, then it should be
possible to use it on msvc builds as well.

On 3/22/21 2:57 PM, Jon Evans wrote:
> Bumping this thread as we don't seem to have a resolution yet.
> 
> The Windows vcpkg package works as there is still a config.h with the
> version in the "visualc" directory.
> 
> But, MacOS doesn't build and I guess some Linux distros don't either.
> 
> Can we make pkg-config work for MacOS?
> 
> On Wed, Feb 3, 2021 at 1:45 PM Carsten Schoenert
> mailto:c.schoen...@t-online.de>> wrote:
> 
> Am 03.02.21 um 13:03 schrieb jp charras:
> > OTOH, a version.h file is not a bad idea (read: for me a very good
> idea):
> >
> > at least the name is already a useful comment and it request only
> a very
> > few amount of work.
> >
> > Many tools use this trick (for instance opencascade, and most of
> other
> > tools we are using in Kicad), and one **big** advantage it works
> outside
> > the libtool stuff.
> 
> For simple things like version detection pkg-config is already enough,
> no need for mostly incompatible hacks. Even different shells on the same
> host can behavior really unexpected.
> 
> If you need to detect the version of ngspice you will need to do this
> this already before any build is started.
> 
> > $ pkg-config --modversion ngspice
> > 33
> -- 
> Regards
> Carsten
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to     : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Jon Evans]

Bumping this thread as we don't seem to have a resolution yet.

The Windows vcpkg package works as there is still a config.h with the
version in the "visualc" directory.

But, MacOS doesn't build and I guess some Linux distros don't either.

Can we make pkg-config work for MacOS?

On Wed, Feb 3, 2021 at 1:45 PM Carsten Schoenert 
wrote:

> Am 03.02.21 um 13:03 schrieb jp charras:
> > OTOH, a version.h file is not a bad idea (read: for me a very good idea):
> >
> > at least the name is already a useful comment and it request only a very
> > few amount of work.
> >
> > Many tools use this trick (for instance opencascade, and most of other
> > tools we are using in Kicad), and one **big** advantage it works outside
> > the libtool stuff.
>
> For simple things like version detection pkg-config is already enough,
> no need for mostly incompatible hacks. Even different shells on the same
> host can behavior really unexpected.
>
> If you need to detect the version of ngspice you will need to do this
> this already before any build is started.
>
> > $ pkg-config --modversion ngspice
> > 33
> --
> Regards
> Carsten
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Carsten Schoenert]

Am 03.02.21 um 13:03 schrieb jp charras:
> OTOH, a version.h file is not a bad idea (read: for me a very good idea):
> 
> at least the name is already a useful comment and it request only a very 
> few amount of work.
> 
> Many tools use this trick (for instance opencascade, and most of other 
> tools we are using in Kicad), and one **big** advantage it works outside 
> the libtool stuff.

For simple things like version detection pkg-config is already enough,
no need for mostly incompatible hacks. Even different shells on the same
host can behavior really unexpected.

If you need to detect the version of ngspice you will need to do this
this already before any build is started.

> $ pkg-config --modversion ngspice
> 33
-- 
Regards
Carsten

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Carsten Schoenert]

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 to
integrate the things correctly into configure.ac and potential
Makefile(s).am.

If I'm feeling boring enough I can try to have look this. But ngspice
did already cost a lot of my brain in the past. :P

> What about adding and distributing alongside of sharedspice.h a version 
> header file verngspice.h which contains only some version info?

That would for sure help for the problem Ian has written about, but it
doesn't solves the underlying real problem, a non versioned library.

To add such a version string you even don't need to add another header
file, there is already sharedspice.h available. It's easy to process
this as .h.in file while configure is running to add such a version
string. I can try to have a look at this as well.

-- 
Regards
Carsten

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Holger Vogt]

I remember some time ago I tried to address the libtool versioning, but 
I did not understand it, so abandoned it again.


What about adding and distributing alongside of sharedspice.h a version 
header file verngspice.h which contains only some version info?



Holger

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Ian McInerney]

On Wed, Feb 3, 2021 at 7:34 AM Holger Vogt  wrote:

> To obtain version information of the currently available libngspice-0.so
> version, you might do the following:
>
> load libngspice-0 dynamically
> initialze libngspice
> send the command 'version -s'
> retrieve some text response similar to the following:
>
> **
> ** ngspice-34
> ** Please get your ngspice manual from
> http://ngspice.sourceforge.net/docs.html
> ** Please file your bug-reports at
> http://ngspice.sourceforge.net/bugrep.html
> ** Creation Date: Fri Jan 29 14:27:27 UTC 2021
> **
>
> check for ngspice, get the version number
> unload libngspice
>
>
There was a discussion about retrieving the version information here:
https://gitlab.com/kicad/code/kicad/-/issues/4833, and it looks like Holger
even mentioned that config.h includes the version information so that is
why Wayne used it. The main thing is, having to load the simulator just to
get the version information is a very complicated thing for our system to
handle. The ngspice code in KiCad is only in one specific window, and the
help windows are available from all programs. The reason the build-time
info (from config.h) was chosen is because that information can be exposed
to all the help windows and included in the version string the entire time.

-Ian
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Carsten Schoenert]

Am 03.02.21 um 08:34 schrieb Holger Vogt:
> To obtain version information of the currently available libngspice-0.so 
> version, you might do the following:
> 
> load libngspice-0 dynamically
> initialze libngspice
> send the command 'version -s'
> retrieve some text response similar to the following:
> 
> **
> ** ngspice-34
> ** Please get your ngspice manual from 
> http://ngspice.sourceforge.net/docs.html
> ** Please file your bug-reports at 
> http://ngspice.sourceforge.net/bugrep.html
> ** Creation Date: Fri Jan 29 14:27:27 UTC 2021
> **
> 
> check for ngspice, get the version number
> unload libngspice

I'd say the only reliable long term way is to add a proper libtool
versioning with correct API/ABI integration in ngspice. All other things
will break on various ends again and again and will become PITA.
ngspice-34 comes with new symbols since at least version 28.

-- 
Regrads
Carsten

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Holger Vogt]

To obtain version information of the currently available libngspice-0.so 
version, you might do the following:


load libngspice-0 dynamically
initialze libngspice
send the command 'version -s'
retrieve some text response similar to the following:

**
** ngspice-34
** Please get your ngspice manual from 
http://ngspice.sourceforge.net/docs.html
** Please file your bug-reports at 
http://ngspice.sourceforge.net/bugrep.html

** Creation Date: Fri Jan 29 14:27:27 UTC 2021
**

check for ngspice, get the version number
unload libngspice


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Carsten Schoenert]

Hello,

Am 02.02.21 um 22:07 schrieb Jean-Samuel Reynaud:
> FYI:
> As I see the PATH for the file ngspice/config.h is changed on
> ngspice-34. And on debian package this file is no more distributed on
> this version (as I see on last updated package).
> 
> So there is an impact on some KiCad code:
> 
> common/build_version.cpp:161:#include 

including a build specific header file from a depending component could
never be correct.

I dropped a note about that behavior of ngspice to ship the config.h
file some versions ago to Holger, but let the shipped header file within
the package. That's now gone.
Holger modified the configuration of ngspice so that the dist target of
ngspice isn't packaging config.h into the tarball that is correct, it's
(re-)created while the configure run.

I've no idea what functions did get included from ngspice/config.h
within kicad, but the only correct header file for including external
function is ngspice/sharedspice.h in case.

Starting a KiCad 5.1.9 together with libngspice0 34 works without
problems so far I could test it.

-- 
Regards
Carsten

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Jean-Samuel Reynaud]

FYI:
As I see the PATH for the file ngspice/config.h is changed on
ngspice-34. And on debian package this file is no more distributed on
this version (as I see on last updated package).

So there is an impact on some KiCad code:

common/build_version.cpp:161:#include 



Le 02/02/2021 à 09:16, Holger Vogt a écrit :
> We don't install cmpp and dlmain.c any more.
> 
> We also don't install the headers any more, except for sharedspice.h.
> 
> Holger
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Holger Vogt]

We don't install cmpp and dlmain.c any more.

We also don't install the headers any more, except for sharedspice.h.

Holger

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Nick Østergaard]

Hi Holger,

Whats up with this big diff from 33 to 34?

https://github.com/msys2/MINGW-packages/pull/7867#issuecomment-770786574

Nick

On Sat, 30 Jan 2021 at 17:57, Wayne Stambaugh  wrote:
>
> Holger,
>
> Thanks for the fixes.  Hopefully our packagers can get this into as many
> of our nightly builds as feasible.  I know there will likely be some
> distro related packaging issues but we should be able to support a large
> number of builds.
>
> Cheers,
>
> Wayne
>
> On 1/30/21 10:10 AM, Holger Vogt wrote:
> > ngspice-34 is available.
> >
> >
> > Some of the recent issues (such as
> > https://gitlab.com/kicad/code/kicad/-/issues/7180) have been fixed.
> >
> >
> > Holger
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ngspice-34

[Wayne Stambaugh]

Holger,

Thanks for the fixes.  Hopefully our packagers can get this into as many
of our nightly builds as feasible.  I know there will likely be some
distro related packaging issues but we should be able to support a large
number of builds.

Cheers,

Wayne

On 1/30/21 10:10 AM, Holger Vogt wrote:
> ngspice-34 is available.
> 
> 
> Some of the recent issues (such as
> https://gitlab.com/kicad/code/kicad/-/issues/7180) have been fixed.
> 
> 
> Holger
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] ngspice-34

[Holger Vogt]

ngspice-34 is available.


Some of the recent issues (such as 
https://gitlab.com/kicad/code/kicad/-/issues/7180) have been fixed.



Holger



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp