That search path is not complied into ngspice at all. It works for me both
inside and outside of Applications, and renamed. I do not have ngspice
installed anywhere on my computer, and those downloaded installs work for
me where ever I place them. I did not test as standalone or not, but I
will test that as well.
Adam
On Thu, Oct 3, 2019, 5:01 AM Jonatan Liljedahl <email address hidden>
wrote:
> BTW, it only works if KiCad is installed in /Applications/KiCad/,
> otherwise it can't find the code model files. Is this search path a
> compile time constant, or could it instead look in the actual running
> app bundle? A user might install it in ~/Applications/KiCad/ instead, or
> /Applications/KiCad_testing etc..
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835296
>
> Title:
> simulating laser_driver on macos nightly causes segfault
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1835296/+subscriptions
>
Hi Jonatan,
That search path is not complied into ngspice at all. It works for me both
inside and outside of Applications, and renamed. I do not have ngspice
installed anywhere on my computer, and those downloaded installs work for
me where ever I place them. I did not test as standalone or not, but I
will test that as well.
Adam
On Thu, Oct 3, 2019, 5:01 AM Jonatan Liljedahl <email address hidden>
wrote:
> BTW, it only works if KiCad is installed in /Applications/ KiCad/, KiCad/ instead, or KiCad_testing etc.. /bugs.launchpad .net/bugs/ 1835296 /bugs.launchpad .net/kicad/ +bug/1835296/ +subscriptions
> otherwise it can't find the code model files. Is this search path a
> compile time constant, or could it instead look in the actual running
> app bundle? A user might install it in ~/Applications/
> /Applications/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> simulating laser_driver on macos nightly causes segfault
>
> To manage notifications about this bug go to:
> https:/
>