On Thu, Oct 3, 2019 at 10:05 AM Adam Wolf <email address hidden> wrote:
>
> Hi folks,
>
> It works for me on those october builds in both standalone eeschema
> and in regular kicad, in Applications and outside of Applications.
> Please confirm that you are not starting eeschema before opening kicad
> one time. It is required that kicad be opened one time before
> starting eeschema, due to some macOS technicalities.
>
> I am no longer seeing this issue.
>
> If I build ngspice31-2 with --enable-debug=yes, then the issue comes
> back. ngspice 28 works with both debug enabled and disabled, but 31-2
> does not. I have switched nightlies to use 31-2 to --disable-debug,
> and that's what is in the October nightly builds. Holger--when you
> hear from the mac package for ngspice, that would be awesome. I would
> love to compile with the same flags as they do for increased
> compatibility reasons.
>
> I appreciate everyone's patience around this issue. I have other very
> pressing issues with macOS packaging that also need my attention, but
> I'm giving most of my attention to this ticket since it is the loudest
> :)
It is possible that we need to investigate NGSPICE: :findCmPath( ) in /github. com/KiCad/ kicad-source- mirror/ blob/e5463b5455 14ddfc849c6985e 8884d1dec5edd3b /eeschema/ sim/ngspice. cpp.
https:/
On Thu, Oct 3, 2019 at 10:05 AM Adam Wolf <email address hidden> wrote:
>
> Hi folks,
>
> It works for me on those october builds in both standalone eeschema
> and in regular kicad, in Applications and outside of Applications.
> Please confirm that you are not starting eeschema before opening kicad
> one time. It is required that kicad be opened one time before
> starting eeschema, due to some macOS technicalities.
>
> I am no longer seeing this issue.
>
> If I build ngspice31-2 with --enable-debug=yes, then the issue comes
> back. ngspice 28 works with both debug enabled and disabled, but 31-2
> does not. I have switched nightlies to use 31-2 to --disable-debug,
> and that's what is in the October nightly builds. Holger--when you
> hear from the mac package for ngspice, that would be awesome. I would
> love to compile with the same flags as they do for increased
> compatibility reasons.
>
> I appreciate everyone's patience around this issue. I have other very
> pressing issues with macOS packaging that also need my attention, but
> I'm giving most of my attention to this ticket since it is the loudest
> :)