KiCad

Bug #1630676
Comment #16

Comment 16 for bug 1630676

Revision history for this message

Wayne Stambaugh (stambaughw) wrote on 2016-10-13: Re: [Bug 1630676] Re: Simulator freezes until return is pressed in terminal

#16

While I applaud your effort, I'm not thrilled with the prospect of using
the development version of ngspice let alone using a third party repo of
a the development version of ngspice with custom changes. This is not
something I can endorse. As I have already explained, the issue can be
resolved by copying a properly constructed spinit file in
${install_path}/bin on windows. I still think this is a packaging
configuration issue. My guess it that a similar concept would work on
osx but I don't have access to an osx system to confirm this. I haven't
seen any feedback from the osx devs on this. I'm leaving this fix for
this up to developer who made ngspice a dependency. He knows who he is. ;)

On 10/13/2016 9:16 AM, Jonatan Liljedahl wrote:
> Hi Holger,
>
> OSX has "HOME" env variable as well. However, it's also common to use
> ~/Library/Application Support/TheAppName/ as a folder for app-specific
> stuff. For example, Kicad is supposed to look in ~/Library/Application
> Support/kicad/scripting/plugins/ for python footprint wizards (but
> some other bug make it not see it currently).
>
> Perhaps it makes sense to use ${HOME}/.spiceinit for ngspice, since
> that's how it works on other platforms.
>
> On Thu, Oct 13, 2016 at 1:36 PM, Holger Vogt <email address hidden> wrote:
>> just a correction:
>>
>> Concernimg .spiceinit of course
>>
>> Holger
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1630676
>>
>> Title:
>> Simulator freezes until return is pressed in terminal
>>
>> Status in KiCad:
>> New
>>
>> Bug description:
>> Most often (but sometimes not), running the simulator freezes the app,
>> until one switches to the terminal where kicad was started[1] and
>> press the return key a number of times, then the simulation completes.
>> There's no errors or Y/n questions in the simulator log or in the
>> terminal.
>>
>> [1] - At least on OSX, kicad must be started from the terminal with
>> proper environment variable set to make it find the needed ngspice
>> init file and codemodels.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/kicad/+bug/1630676/+subscriptions
>
>

While I applaud your effort, I'm not thrilled with the prospect of using
the development version of ngspice let alone using a third party repo of
a the development version of ngspice with custom changes.  This is not
something I can endorse.  As I have already explained, the issue can be
resolved by copying a properly constructed spinit file in
${install_path}/bin on windows.  I still think this is a packaging
configuration issue.  My guess it that a similar concept would work on
osx but I don't have access to an osx system to confirm this.  I haven't
seen any feedback from the osx devs on this.  I'm leaving this fix for
this up to developer who made ngspice a dependency.  He knows who he is. ;)

On 10/13/2016 9:16 AM, Jonatan Liljedahl wrote:
> Hi Holger,
> 
> OSX has "HOME" env variable as well. However, it's also common to use
> ~/Library/Application Support/TheAppName/ as a folder for app-specific
> stuff. For example, Kicad is supposed to look in ~/Library/Application
> Support/kicad/scripting/plugins/ for python footprint wizards (but
> some other bug make it not see it currently).
> 
> Perhaps it makes sense to use ${HOME}/.spiceinit for ngspice, since
> that's how it works on other platforms.
> 
> On Thu, Oct 13, 2016 at 1:36 PM, Holger Vogt <1630676@bugs.launchpad.net> wrote:
>> just a correction:
>>
>> Concernimg .spiceinit of course
>>
>> Holger
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1630676
>>
>> Title:
>>   Simulator freezes until return is pressed in terminal
>>
>> Status in KiCad:
>>   New
>>
>> Bug description:
>>   Most often (but sometimes not), running the simulator freezes the app,
>>   until one switches to the terminal where kicad was started[1] and
>>   press the return key a number of times, then the simulation completes.
>>   There's no errors or Y/n questions in the simulator log or in the
>>   terminal.
>>
>>   [1] - At least on OSX, kicad must be started from the terminal with
>>   proper environment variable set to make it find the needed ngspice
>>   init file and codemodels.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/kicad/+bug/1630676/+subscriptions
> 
>