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 :
15 matches
Mail list logo
