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 :
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
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
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
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
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
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
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
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
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
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
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?
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
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
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
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
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.
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
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
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 :
> 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
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,
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
>
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
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
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
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
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
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:
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,
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 :
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
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
35 matches
Mail list logo
