No problem. I can built ngspice from source code from their git repository. Maybe we need to find some guys to help us to modify Ngpsice source codes. Then EE simulation will be much faster( We can integrate EE model in source code and a good way to find EE's libs and give a good wave data), and will give our users more friendly error or warming message. I can do this, I don't have enough time. :) Thanks.

Yeay! That's fixed it!! :) "Maybe we need to find some guys to help us to modify Ngpsice source codes. Then EE simulation will be much faster( We can integrate EE model in source code and a good way to find EE's libs and give a good wave data), and will give our users more friendly error or warming message. " That would be a very good idea. i) We need to have a way to do .step and .meas functions. ii) The EE waveform display is nice but it soon gets hard to read with more than 2 or 3 traces. There needs to be a way to put traces into separate graphs (like ngspice.com, LTspice and CL) iii) Better cursors to show deltaX and deltaY iv) There also needs to be a way to do plot arithmetic. Plotting a frequency response as a Bode plot of V(out)/V(in) for a simple amplifier works OK: http://localhost/easyeda/file_view_MAXIM-opamp-stage-gain_7GASM4mEW.htm but trying to plot the loop gain as a Bode plot of V(out)/V(fb): http://localhost/easyeda/file_view_MAXIM-opamp-loop-gain_ImRLFXf9r.htm is not possible. Using the `par(’expression’)` (ngspice manual section 15.4.10 ) like this: `.save loopgain = V(out)/V(fb)` does not produce the right output when plotted in a .ac simulation. Loop gain is a very important thing to be able to plot because it is the graph that shows gain and phase margins. Important stuff for SMPS and Control System design! Audio amplifier designers will be interested in it too.

Making a good wave view is our plan, this is a big thing for EE.