Comment 6 for bug 1630676

Hey Orson,

I see a problem with your solution on Linux. On linux, the default
spinit file will work out without any changes. Ignoring it may cause
issues for advanced users who use custom settings. I know I wouldn't be
very happy if my settings that I spent a lot of time researching were
ignored by kicad.

My preference is to see if you can get the relative path solution
working so that a reasonable default can be provided in the installer
which would be a better all around solution. This would also give
advanced users an option to configure ngspice to suit their needs.

There is a lot of individual knowledge acquired while trying to figure
out some of the issues with the simulation. I'm assuming you are going
to provide documentation for the simulator so please make sure this
local knowledge makes it's way into that documentation. I'm sure these
issues will pop up once more users start using the simulator. I would
rather not have to keep rehashing this issue.

Thanks,

Wayne

On 10/6/2016 3:42 AM, Maciej Sumiński wrote:
> Hi Wayne,
>
> I see the following options, both start with forcing ngspice to ignore the default spinit file (e.g. by setting SPICE_SCRIPTS env var to a not existing directory):
> - Manually issue commands to load .cm files and enable nomoremode (having it disabled apparently can freeze the simulator and gives no benefits here). This way we can have a list of directories to be checked and pick the one which in fact contains .cm files.
> - Load the spinit file in KiCad and execute the stored commands with adjusted paths.
>
> Alternatively, we can override the SPICE_SCRIPTS env variable to contain
> a relative path to spinit, and make it contain relative paths as well.
> It will solve the problem for KiCad installers/packagers, but not for
> the others.
>