Thank you very much for the thorough answer! I'll follow you advice and see what I can do...
On Tuesday, June 21, 2016 at 4:04:46 AM UTC+2, Gavin wrote: > > Sorry, I don't have a Mac. So I cannot say for sure, but I believe it is > only an issue with the LTSPICE Mac version (LTspiceIV.dmg). It seems like > the LTSPICE Mac version does not take command line input. > > The following site mentions that -ascii did not work with the LTSPICE Mac > version: > > > http://stackoverflow.com/questions/32772832/ltspice-command-line-options-ascii-not-found-on-mac > > In addition, the following sites mention that the LTSPICE Mac version was > missing a number of features that the Windows version has: > > > http://www.diyaudio.com/forums/software-tools/263111-ltspice-imac-sucks-huge.html > http://irust.in/using-the-windows-version-of-ltspice-on-a-mac-running-osx/ > http://www.jackenhack.com/use-ltspice-iv-windows-version-mac-os/ > > That seems to support that the LTSPICE Mac version is likely missing the > command line functionality that the Windows version has. To verify whether > that is the case or not, you would probably have to contact Technical > Support at Linear Technology [ http://www.linear.com/contact/ ]. > > A workaround should be to install the LTSPICE Windows version > (LTspiceIV.exe) on your Mac using Wine or Winebottler as mentioned on the > web pages at the above links. > > The following site contains information for using LTSPICE with Wine on > Linux, but it might also help for using LTSPICE with Wine on Mac: > > http://cmosedu.com/jbaker/students/wenlan/Electricwu.htm > > Hope that helps and good luck. > > On 6/20/2016 10:19 AM, Tim Molter wrote: > > > Here's the window I get: > > > > <https://lh3.googleusercontent.com/-1nsTcgIkDj0/V2gWzF2XuRI/AAAAAAAADp4/SLtaSJZQjXsNq4U7BwI_KJumQkp2UQt7ACLcB/s1600/Screen%2BShot%2B2016-06-20%2Bat%2B6.15.56%2BPM.png> > > > The command I have set up in Electric is: > > Run: > > > /opt/homebrew-cask/Caskroom/ltspice/latest/LTspice.app/Contents/MacOS/LTspice > > With Args: > > -i ${FILENAME} -r ${FILENAME_NO_EXT}.raw -o ${FILENAME_NO_EXT}.out > > I believe it is supposed to just open up the spi file automatically. Any > ideas? Is it only a Mac thing? Or is there a known workaround? > > -- You received this message because you are subscribed to the Google Groups "Electric VLSI Editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
